Yes, especially with the limited error messages SLICC spits out at the moment. When they aren't deleted it's difficult to even narrow down how far SLICC makes it before it fails; If they are deleted you can at least get an idea of which file SLICC gets stuck on.
-Derek On Mon, Aug 3, 2009 at 8:53 PM, nathan binkert<[email protected]> wrote: >> The command: >> >> scons -c >> >> does not appear to remove SLICC generated files in mem/protocol (nor >> does scons -c <target>). I think it would be helpful if it did to >> avoid confusion about whether or not you're looking at a recently >> generated file. How can this be done? > > I just checked and the only files that are left there are a bunch of > autogenerated header files that essentially just link to other header > files. These are not actually generated by slicc. Are these files a > problem? > > 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
