This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: class initialization check overhead
- From: Jeff Sturm <jsturm at one-point dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Kresten Krab Thorup '" <krab at trifork dot com>, "'java at gcc dot gnu dot org '" <java at gcc dot gnu dot org>
- Date: Fri, 25 Oct 2002 08:37:30 -0400 (EDT)
- Subject: RE: class initialization check overhead
On Thu, 24 Oct 2002, Boehm, Hans wrote:
> We need to be careful about memory ordering issues in this code. On
> current X86 processors it's probably OK. On Itanium the test needs to
> involve an aquire load. On some some other architectures a barrier is
> needed to ensure that loads following the test really can't see the
> preinitialization values.
Would declaring the test variable with java volatile be sufficient?
(Assuming "volatile" is actually implemented?)
Jeff