This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the GCJ project. See the GCJ home page for more information.
> Compiling each .class file into a single .o file will leave alot of > duplicated UTF8 constants and the like in constant pools. There's no way, > barring much hacking on assemblers, binary standards, and linkers to atomize > all this in the linker, Well, the GNU tools already do support merging duplicates when using ELF, though jc1 does not use this fayire yet. > so it would be sort of nice if gcj could take multiple > ..class files and produce a single .o file with all the constant pools > merged. jc1 can compile an entire .zip.jzr file as a unit. The constant pools are not merged, but there is only a single copy of each UT8 constant. When doing static linking, the plan is to do away with UTF8 constants for string literals. Instead, the compiler generates mangled undefined references, and the linker will pre-allocated static String objects. (However, this will probably not happen soon.) --Per Bothner Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner