Dave Korn wrote: > Not simple, but not so hard as to be impossible either; as it turns out, the > internal structure of libgcj looks a lot like a turnip, with a bunch of skinny > branchy foliage waving around on top, a few shallow roots spreading under the > ground, and a big ball of hair in the middle holding it all together, which > makes it actually quite easy to manually find a partition. > > There are a couple of regressions to solve first, but it appears that I've > more-or-less cracked it. Full details are written up here: > > http://gcc.gnu.org/wiki/Internal_dependencies_of_libgcj
Thank you for this. One thing that you may like to consider is compiling more packages with -findirect-dispatch -fno-indirect-classes. This has a smallish performance penalty, but packages compiled this way have no link- time dependencies on other packages. Instead, everything gets fixed up at runtime. Andrew.
