This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: about non-compatible optimization (was: Re: patch to bring java vtables closer to g++ abi conformance)
- From: "Tuomas Leikola" <tuomas dot leikola at digia dot com>
- To: <java at gcc dot gnu dot org>
- Date: Tue, 29 Jan 2002 13:30:46 +0200
- Subject: Re: about non-compatible optimization (was: Re: patch to bring java vtables closer to g++ abi conformance)
----- Original Message -----
From: "Bryce McKinlay" <bryce@waitaki.otago.ac.nz>
To: "Tuomas Leikola" <tuomas.leikola@digia.com>
Cc: <java@gcc.gnu.org>; <shudo@computer.org>
Sent: Tuesday, January 29, 2002 2:25 AM
Subject: Re: about non-compatible optimization (was: Re: patch to bring java
vtables closer to g++ abi conformance)
> However the real reason static is so
> much slower here is due to GCJ adding a class initialization check to
> the start of every static method. I think we can do better by putting
> this check at the call site rather than in the method.
ouch. is there a way to avoid this? -finitialize-all-classes-at-startup or
something
theoretically, if there are no dynamically loaded classes
(-fno-dynamic-loading) class init checks can be propagated all the way to
main().. getting past the if (cannot==fail) would need tree magic i think.