Is something coined as "derived" from a particular code because it uses the same interface? In some sense, any code you do within M5 has to be using that interface in order for it to work. Thus, isnt anything conforming to the whatever interface is defined "derived"?
My comments: > interrupts.cc seems to be derived from alpha/interrupts.hh - commented code needs to be deleted - implementation of functions different, interface is the same... - probably just MIPS (c) > linux/linux.hh is exactly the same as alpha/linux/linux.hh with some > constants changed - agree - just UM (c) > linux/linux.cc is s/AlphaLinux/MipsLinux/g of alpha/linux/linux.cc - agree - just UM (c) > mips_core_specific.cc is ev5.cc with most of the code commented out - commented code should be probably be deleted. - i know have things for that file or intend to move things into that file actually, but oh well... - UM (c) > utility.cc has 25 lines verbatim from alpha/utility.cc - i dont remember coding that getArgument() 25 lines. Gabe? - MIPS (c) and I guess a UM (c) for that 25 lines > regfile.cc is very similar to sparc/regfile.cc - eeeeh, tricky here, cuz I recoded this a bunch of times to match Gabe's interface when we started the architectures a long time ago.. - MIPS (c) + UM (c) -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
