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
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.
Ok. I spent some time trying
The parsing errors are much better. Thanks!
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On Behalf Of
nathan binkert
Sent: Tuesday, August 04, 2009 9:38 AM
To: M5 Developer List
Subject: Re: [m5-dev] Scons cleaning
Yes, especially
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?
-Derek
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
