Test

Thu Sep 17 07:19:00 GMT 1998

On 1998年9月16日, Per Bothner wrote:
>> OK but that sort of sidesteps the issue. What if for some reason one 
>> wanted to produce a statically linked executable with minimal 
>> footprint, i.e., just the required classes? Will that be an option?
>>Well, that sort of follows from using libjava.a - standard linker
>technology leaves out unreferenced .o files, when doing a static
>link. Normally, we would compile each java class to a single .o file.
>(Actually, it may make sense to have a somewhat smarter linker,
>but that's more detail than I feel like getting into.)
>
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, 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.
--
Jon Olson, Modular Mining Systems
	 3289 E. Hemisphere Loop
	 Tucson, AZ 85706
INTERNET: olson@mmsi.com
PHONE: (520)746-9127
FAX: (520)889-5790