public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Archie Cobbs <archie@dellroad.org>
To: Mark Wielaard <mark@klomp.org>
Cc: classpath-patches@gnu.org, mauve-patches@sources.redhat.com
Subject: Re: [cp-patches] Logger initialization regression fix and a little  story on security contexts during class initialization
Date: Thu, 11 May 2006 13:49:00 -0000	[thread overview]
Message-ID: <4463414C.6010802@dellroad.org> (raw)
In-Reply-To: <1147350676.7640.40.camel@localhost.localdomain>

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

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com

  reply	other threads:[~2006-05-11 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 12:33 Mark Wielaard
2006-05-11 13:49 ` Archie Cobbs [this message]
2006-05-14 15:06   ` [cp-patches] " Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4463414C.6010802@dellroad.org \
    --to=archie@dellroad.org \
    --cc=classpath-patches@gnu.org \
    --cc=mark@klomp.org \
    --cc=mauve-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).