> So far I've found two oddities with a straightforward implementation of this > approach: > > (1) It breaks down when the target is a prefix of the source: > > [ STRIP] ALPHA_SE/m5.fast.unstripped -> > > instead of > > [ STRIP] ALPHA_SE/m5.fast: .unstripped -> > > (2) It gives the wrong impression when targets are in a parent directory > relative to the source: > > [ISA DESC] ALPHA_SE/arch/alpha/isa/main.isa -> decoder.cc, decoder.hh, > max_inst_regs.hh, atomic_simple_cpu_exec.cc, inorder_cpu_exec.cc, > o3_cpu_exec.cc, timing_simple_cpu_exec.cc > > instead of > > [ISA DESC] ALPHA_SE/arch/alpha: isa/main.isa -> decoder.cc, decoder.hh, > max_inst_regs.hh, atomic_simple_cpu_exec.cc, inorder_cpu_exec.cc, > o3_cpu_exec.cc, timing_simple_cpu_exec.cc > > I don't see these as deal-breakers, and I'm fine with leaving them as they > are unless someone has a reasonable idea about how to address them, but I > thought I'd point out that the ambiguities aren't purely theoretical.
hmmm.... I guess I still like the ability to cut and paste, but the ambiguity is annoying (and there are bound to be others. I'll let you decide. For #2, you could do ../decoder.cc, for #1, if you want, you could detect that the RHS is empty and do the whole basename. These ideas might be overkill. (Don't you love how a simple idea always gets more complicated?) Nate _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
