This is the mail archive of the
mailing list for the Mauve project.
Re: [cp-patches] Logger initialization regression fix and a little story on security contexts during class initialization
- From: Archie Cobbs <archie at dellroad dot org>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: classpath-patches at gnu dot org, mauve-patches at sources dot redhat dot com
- Date: Thu, 11 May 2006 08:51:08 -0500
- Subject: Re: [cp-patches] Logger initialization regression fix and a little story on security contexts during class initialization
- References: <email@example.com>
Mark Wielaard wrote:
We had an interesting regression with the logging code in GNU Classpath.
It wasn't immediately apparent because it was only caused with certain
compilers. The class initialization order was subtly different between
byte code compiled with gcj -C and jikes. So it didn't show up with gcj
-C which I used when committing this code.
Since class initialization is strictly defined by the JVM spec,
doesn't this necessarily imply a bug in either gcj or jikes?
The only other alternative is that they both compile the same code
correctly, but do so differenly enough to change the class initialization
order, which to me seems even more surprising (but possible I guess.. ?)
Archie Cobbs * CTO, Awarix * http://www.awarix.com