lobotomizing libgcj

Jeff Sturm jsturm@one-point.com
Fri May 11 16:46:00 GMT 2001


On Fri, 11 May 2001, Tony Kimball wrote:
> How about emitting a .o per method, as well as one for the class?

What's the benefit vs. one section per method, as Tom suggested?

In any case, you need to prevent the vtable from linking all the instance 
methods in.  The c++ frontend has a mechanism called vtable-gc, if that
still works.

Jeff





More information about the Java mailing list