> I'm sure it's feasible, but I doubt it's worth it. Since the isa parser > runs as a single pass that generates all the files in one shot (and I don't > necessarily expect this to change), there's really no benefit in knowing > which files have changed, or which subset of inputs depend on the changed > file(s). All you need to know is that some input file has changed. If the > input change only affects a subset of the outputs, then scons (and in fact > the isa parser itself) will handle that automatically and avoid recompiling > unchanged outputs.
Ok. Makes sense. We deal with SLICC files and python similarly. The only place where I think that some automatic detection might make sense is in the src/python/m5 directory. Be annoying to recompile the ISA when a change to unrelated params takes place. I'm not sure if the ISA parser uses m5.utils, but it probably should. Nate _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
