public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42811] [4.5 regression] java.lang.ExceptionInInitializerError in ecj1
Date: Wed, 12 May 2010 22:20:00 -0000 [thread overview]
Message-ID: <20100512222030.18344.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42811-13856@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from davek at gcc dot gnu dot org 2010-05-12 22:20 -------
(In reply to comment #22)
> Hm, I'm not able to run thread_test.c and thread_leak_test.c tests using "make
> -k check", so otherwise deadly trivial patch can't be fully tested.
>
Well I can't approve it but I think it's as close to "obvious" as anything
gets. If you send it to libjava-patches (and cc the upstream list for
boehm-gc: <gc@napali.hpl.hp.com> - we're trying to avoid any divergence), I
can't imagine anyone would object. Thanks for helping track this down :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42811
next prev parent reply other threads:[~2010-05-12 22:20 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:51 ` davek at gcc dot gnu dot org
2010-03-20 20:02 ` davek at gcc dot gnu dot org
2010-03-20 20:22 ` rguenth at gcc dot gnu dot org
2010-03-20 20:34 ` 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:42 ` 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:02 ` ubizjak at gmail dot com
2010-05-10 20:54 ` davek at gcc dot gnu dot org
2010-05-12 9:47 ` ubizjak at gmail dot com
2010-05-12 16:49 ` davek at gcc dot gnu dot org
2010-05-12 17:40 ` ubizjak at gmail dot com
2010-05-12 17:47 ` 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 [this message]
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=20100512222030.18344.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).