This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: duplicate class registration fix?
- From: Tom Tromey <tromey at redhat dot com>
- To: nferrier at tapsellferrier dot co dot uk
- Cc: java at gcc dot gnu dot org
- Date: 06 Nov 2002 09:45:48 -0700
- Subject: Re: duplicate class registration fix?
- References: <ud6pl61zk.fsf@tapsellferrier.co.uk>
- Reply-to: tromey at redhat dot com
>>>>> "Nic" == Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:
Nic> Perhaps someone who knows about GCJ might spot why the above would be
Nic> a bad thing to do?
As Jeff points out, this was talked about in the original post.
Long term, perhaps indirect-dispatch is going to help here. If
somebody finishes it :-)
Actually, I like indirect-dispatch more and more. It seems like it
could also help us with class initialization. We could have calls to
static methods first be directed to a stub that initializes the class
and changes the static method "vtable" to point to the real methods.
(This may be more expensive than what we have now. But it is worth a
try.)
Tom