This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ: Trouble with static initialization
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: "Craig A. Vanderborgh" <craigv at voxware dot com>, java at gcc dot gnu dot org
- Date: 16 Jul 2003 09:10:01 -0600
- Subject: Re: GCJ: Trouble with static initialization
- References: <Pine.LNX.4.44.0307142333020.19718-100000@ops2.one-point.com>
- Reply-to: tromey at redhat dot com
Jeff> I'm not aware of any gcj bugs in this area, aside from possible
Jeff> race conditions on a multiprocessor.
There was one bug in this area not too long ago, fixed here:
2003-03-11 Tom Tromey <tromey@redhat.com>
* parse.y (resolve_field_access): Initialize class if field is
found in another static field.
* expr.c (build_class_init): Don't optimize out initialization of
implemented interface.
This bug was found when building the eclipse java compiler.
I wouldn't rule out the possibility that there are others.
However, this crash was deterministic and debugging showed it to be
lack of correct class initialization pretty quickly.
The current problem's indeterminacy seems to point to something else.
Craig, the most helpful thing would be to have a small test case.
Another useful thing would be to try it on a known-stable platform,
like x86 Linux. That might help narrow the problem down a little.
Tom