Re: gcj executable size reduction?

[Dalibor Topic <robilad at kaffe dot org>]

Tom Tromey wrote:

> Perhaps all we need is a tool that takes a .jar and makes a list of
> all the core classes you need to link in...?

If speed is not an issue, you can use BCEL's verifier to recursively 
descend a class hierarchy starting from a root object.

I've also used jikes in the past, to compile java.lang.Object and let it 
drag in all the dependencies automatically. It mostly works, as far as I 
recall. It's a rather quick way to figure out the 'resident size' of 
your class library.

cheers,
dalibor topic