I think the folks at Wisconsin can best speak about the MIF code generator. It was used to formally verify the correctness of protocols. I'm not sure if any current projects plan to use that support.
The CHECK_INVALID_RESOURCE_STALLS was something I created many years ago to ensure that all memory system resources followed a strict priority and didn't deadlock. Since no currently supported protocols use this feature, it will never be defined as true. I think you are safe to remove it. Brad -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of nathan binkert Sent: Tuesday, August 04, 2009 9:20 AM To: M5 Developer List Subject: Re: [m5-dev] Python SLICC > Just an FYI, I'm currently making changes to both the parser and code > generator. I should be able to push those today if you want to hold > off on the conversion. Ok, no problem. Let me know if you need any help updating parser.py. Also, for those of you SLICC experts out there, I'm curious if either of the following matter anymore (i.e. can they be removed) 1) MIF code generation? I'm guessing that this is actually broken. 2) CHECK_INVALID_RESOURCE_STALLS. Is this ever defined to be true? Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
