public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/42811] [4.5 regression] java.lang.ExceptionInInitializerError in ecj1
Date: Sat, 20 Mar 2010 20:02:00 -0000	[thread overview]
Message-ID: <20100320200235.11842.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42811-13856@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from davek at gcc dot gnu dot org  2010-03-20 20:02 -------
Raising priority P4 -> P3 and Cc'ing RM.

I didn't want to ask to block the release for a bug in a long-neglected
language on a secondary target before I was sure I'd be able to come up with a
fix in time, but now that I have a good fix that has been tested, addresses all
the comments raised in initial reviews, accepted upstream in the relevant
parts, and is just waiting approval, I'd like to make sure it goes in before
you branch; I see we're down to about half-a-dozen P1s now.

Final version of the patch posted at:

http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00931.html


-- 

davek at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu dot
                   |                            |org
           Priority|P4                          |P3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42811


  parent reply	other threads:[~2010-03-20 20:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 23:23 [Bug java/42811] New: " jojelino at gmail dot com
2010-01-20  5:02 ` [Bug java/42811] " jojelino at gmail dot com
2010-01-20 10:48 ` rguenth at gcc dot gnu dot org
2010-01-21  4:55 ` jojelino at gmail dot com
2010-01-22 23:56 ` rguenth at gcc dot gnu dot org
2010-02-04  3:38 ` davek at gcc dot gnu dot org
2010-02-05 17:44 ` davek at gcc dot gnu dot org
2010-02-20  0:40 ` davek at gcc dot gnu dot org
2010-02-27 17:50 ` davek at gcc dot gnu dot org
2010-03-20 20:02 ` davek at gcc dot gnu dot org [this message]
2010-03-20 20:21 ` rguenth at gcc dot gnu dot org
2010-03-20 20:33 ` davek at gcc dot gnu dot org
2010-03-21 19:25 ` [Bug target/42811] " davek at gcc dot gnu dot org
2010-03-21 19:34 ` davek at gcc dot gnu dot org
2010-03-21 19:37 ` davek at gcc dot gnu dot org
2010-03-21 19:41 ` davek at gcc dot gnu dot org
2010-03-21 19:42 ` davek at gcc dot gnu dot org
2010-05-06 16:21 ` davek at gcc dot gnu dot org
2010-05-10 17:01 ` ubizjak at gmail dot com
2010-05-10 20:54 ` davek at gcc dot gnu dot org
2010-05-12  9:46 ` ubizjak at gmail dot com
2010-05-12 16:48 ` davek at gcc dot gnu dot org
2010-05-12 17:39 ` ubizjak at gmail dot com
2010-05-12 17:46 ` ubizjak at gmail dot com
2010-05-12 17:50 ` ubizjak at gmail dot com
2010-05-12 22:20 ` davek at gcc dot gnu dot org
2010-05-12 22:51 ` ubizjak at gmail dot com

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=20100320200235.11842.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).