I was actually thinking about this the other day so I'll chime in. I think the reason SLICC is being run is that you need to see what files it's going to produce to set up dependencies, basically like you might have to do if the ISA parser split up its output files. It might be possible to cache a list of some sort that said what all the input files were last time and check those for changes. If you know what all the input files were last time and none of them changed, presumably the set of input files would end up being the same and so would all the outputs. If any input file changed all bets would be off. I'm not sure how you'd accomplish that in scons, but it might cut out a lot of unnecessary SLICC runs.

Gabe

Quoting Ali Saidi <[email protected]>:

How about a way to make scons not rebuild if there isn't a change?

Ali

On Feb 17, 2011, at 10:21 AM, Korey Sewell wrote:

Thanks Nilay.

I wonder if people think that NO_HTML=True should be the default setting for builds?

On Wed, Feb 16, 2011 at 8:20 PM, Nilay Vaish <[email protected]> wrote:
On Wed, 16 Feb 2011, Korey Sewell wrote:

Hi all,
I noticed that on every build, SLICC wants to parse and generate C++/HTML on
every compile regardless of any changes
to code.

The C++ part seems pretty quick, but the HTML portion hangs slightly.

For the scons "aficionados", how hard would it be to just have SLICC (or
maybe scons) be smart about this and cancel
the rebuild of all the files???

It's probably not a high priority task, but its just one of the things you
notice after compiling a good # of times...

--
- Korey


If you set NO_HTML=True when you issue scons command for compilation, that would prevent html files from being generated.

--
Nilay
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev



--
- Korey
_______________________________________________
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

Reply via email to