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 target/42811] [4.5 regression] java.lang.ExceptionInInitializerError in ecj1 Date: Mon, 10 May 2010 20:54:00 -0000 [thread overview] Message-ID: <20100510205417.19921.qmail@sourceware.org> (raw) In-Reply-To: <bug-42811-13856@http.gcc.gnu.org/bugzilla/> ------- Comment #17 from davek at gcc dot gnu dot org 2010-05-10 20:54 ------- (In reply to comment #16) > On alphaev68-pc-linux-gnu, I'm getting: > FAIL: leaktest > 1 of 4 tests failed > Is this failure something to worry about? The honest answer is: I can't tell you. These are test cases that come with the boehm-gc itself, that have previously been disabled in the gcc import, now I re-enabled them. You won't be suffering from any problem that you didn't already suffer from, in particular w.r.t the use of boehm-gc in libjava, but while it's possible this is a false positive dependent on the precise details of the platform, it's also possible this points to a real unfixed bug. I don't know of any way to tell without really getting down into debugging the internals of the GC to see why it's complaining. But, it's only a new failure because the test didn't used to be run before at all. You're definitely no worse off than you used to be; just now, you know it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42811
next prev parent reply other threads:[~2010-05-10 20:54 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 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 [this message] 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=20100510205417.19921.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: linkBe 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).