On Thu, Jun 9, 2011 at 01:47, Joel Brobecker wrote: > And good to know that this is the last simulator that should be > impacted. If there is a relatively mechanichal way to use sim/common/, > we can look at that option, since the number of simulators to update > would be small (2?).
"no" to all parts unfortunately. the sim/common/ tree is a loose collection of files. sims get to opt in to different pieces or simply re-implement the core functions themselves. i'd say probably more than half do. you can tell quickly by looking at the sub-Makefile and see how many objects from common it refers to. and if the sim still uses "run.c" instead of "nrun.c", you're really screwed. and from what i recall from when i converted bfin from standalone to the common tree, the main loops, header files, and state are heavily impacted. fairly invasive to convert over, but much of it is simply code massage rather than rewriting new stuff. the upside is that the conversion tends to involve throwing out a lot of code because common/ takes care of it for you. the downside is that it isnt trivial, and i unfortunately have no interest in converting other sims. -mike _______________________________________________ Toolchain-devel mailing list Toolchain-devel@blackfin.uclinux.org https://blackfin.uclinux.org/mailman/listinfo/toolchain-devel
