On Mon, Apr 23, 2012 at 10:00 AM, nathan binkert <[email protected]> wrote:
> > Now that I checked, it looks like that's pretty much what you already do > > with the existing .py files in arch/x86/isa/insts. So I guess we could > > just extend that to any other .py files that get created. > > Assuming that import statements are not inside functions and with a > custom importer, one could figure this out without too much trouble. > We could also pretty trivially create a scanner for python. The issue > then is just figuring out the mapping of python module to filename, > but that should be pretty trivial and I think scons knows the details > anyway. > 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. Steve _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
