This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: class initialization check overhead
- From: Tom Tromey <tromey at redhat 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: 14 Dec 2002 13:15:00 -0700
- Subject: Re: class initialization check overhead
- References: <Pine.LNX.4.44.0212141347370.22899-100000@ops2.one-point.com>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
>> (BTW does gcj currently know that vtable slots are immutable? In
>> the past I think I looked at this and decided it didn't know and
>> was therefore missing some potential optimizations. But I haven't
>> looked in quite some time.)
Jeff> I noticed that too. I guess the backend considers all memory to
Jeff> be clobbered by a call, even expressions marked with
Jeff> TREE_READONLY or TREE_CONSTANT. There must be some way to tell
Jeff> the backend that the value at some address will never change.
I know this came up for g++. There was a discussion about it, but I
didn't follow it to its conclusion. But there is an answer out there
somewhere. I'll submit a PR a bit later.
Tom