On Tue, Aug 4, 2009 at 10:46 AM, nathan binkert<[email protected]> wrote: >> I hope you don't mind me asking, but why does the fragility of generated >> code matter? One should never modify generated code and only rarely look at >> it. > > I'm referring to the generator itself. It's pretty hard to follow > what's going on, so if you want to modify the generator itself, you > need to be really careful about it. > >> I'm interested to hear your ideas about how moving SLICC to python helps >> unify the GEMS and M5 configuration. As we all know this is a pretty >> significant challenge that will be solved in multiple steps. I just want to >> make sure we are all on the same path. > > Some of the generator files generate code that takes configuration > parameters. I know that at least StateMachine::printControllerC at > least does. Upon looking at it more closely, maybe this is the only > one that does. So, maybe this isn't a huge benefit, but having an > easier to understand generator should help.
I believe that is correct. For the most part the generator only creates one class (the controller), but splits it up over a bunch of files. There are also some supporting files for the SLICC-defined structs and enums, but those don't take any configuration. > > 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
