This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: class initialization check overhead
- From: Adam Megacz <gcj at lists dot megacz dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Adam Megacz <adam at megacz dot com>, java at gcc dot gnu dot org
- Date: 23 Oct 2002 21:34:48 -0700
- Subject: Re: class initialization check overhead
- Organization: Myself
- References: <Pine.LNX.4.44.0210232230290.10620-100000@ops2.one-point.com>
Jeff Sturm <jsturm@one-point.com> writes:
> Not without doing away with the calling convention, CALL_EXPR, etc.
Is this because there's no way to construct a java/c++ tree that
translates into a bare CALL without breaking abstraction barriers? I
could see how that might be the case.
> Some trapping instruction might be better, like below. This example only
> clobbers eax and memory, and overwrites the single-byte INT3 with one NOP.
Very cool... would this work for references to static members as well?
- a
--
"Through your rags I see your vanity" -- Socrates