On Tue, Jul 21, 2009 at 4:38 PM, nathan binkertn...@binkert.org wrote:
I've noticed that scons creates and runs the SLICC parser every time
you build. Is this absolutely necessary? It seems to slow down the
build quite a bit, especially when recompiling a minor change.
This shouldn't be
Here is an output from a build after nothing changes, where I have the
parser print when it runs.
Which parser? The lex/yacc one or the python one? If it's the
former, I'll try to fix it. If it's the latter, that parser has to be
run, otherwise SCons won't know what files are being
On Tue, Aug 4, 2009 at 2:10 AM, nathan binkertn...@binkert.org wrote:
Here is an output from a build after nothing changes, where I have the
parser print when it runs.
Which parser? The lex/yacc one or the python one?
The Python one.
If it's the
former, I'll try to fix it. If it's the
Which parser? The lex/yacc one or the python one?
The Python one.
If it's the
former, I'll try to fix it. If it's the latter, that parser has to be
run, otherwise SCons won't know what files are being generated. I can
check to see if there is any real performance impact from doing that,
I've noticed that scons creates and runs the SLICC parser every time
you build. Is this absolutely necessary? It seems to slow down the
build quite a bit, especially when recompiling a minor change.
This shouldn't be happening. Does this happen whether or not you make
any changes? Can you
