public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/22084] [4.1 Regression] Divide_1 test case hangs Date: Fri, 24 Jun 2005 09:47:00 -0000 [thread overview] Message-ID: <20050624094716.19808.qmail@sourceware.org> (raw) In-Reply-To: <20050615230348.22084.tromey@gcc.gnu.org> ------- Additional Comments From rmathew at gcc dot gnu dot org 2005-06-24 09:47 ------- Today (20050624, IST), it seems to have become worse. Till now I used to see 2 FAILs, now I see 6 FAILs: FAIL: Divide_1 execution - source compiled test FAIL: Divide_1 output - gij test FAIL: Divide_1 execution - bytecode->native test FAIL: Divide_1 -O3 output - source compiled test FAIL: Divide_1 output - gij test FAIL: Divide_1 -O3 output - bytecode->native test S.N.A.F.U. -- What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2005-06-17 13:13:47 |2005-06-24 09:47:12 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22084
next prev parent reply other threads:[~2005-06-24 9:47 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-15 23:03 [Bug libgcj/22084] New: " tromey at gcc dot gnu dot org 2005-06-17 13:13 ` [Bug libgcj/22084] " rmathew at gcc dot gnu dot org 2005-06-17 13:44 ` dnovillo at redhat dot com 2005-06-17 14:41 ` [Bug libgcj/22084] [4.1 Regression] " pinskia at gcc dot gnu dot org 2005-06-17 17:06 ` tromey at gcc dot gnu dot org 2005-06-18 5:14 ` rmathew at gcc dot gnu dot org 2005-06-24 9:47 ` rmathew at gcc dot gnu dot org [this message] 2005-07-14 18:50 ` pinskia at gcc dot gnu dot org 2005-07-28 4:45 ` phython at gcc dot gnu dot org 2005-07-28 4:51 ` phython at gcc dot gnu dot org 2005-07-28 7:45 ` rmathew at gcc dot gnu dot org 2005-07-28 17:00 ` pinskia at gcc dot gnu dot org 2005-09-09 13:05 ` cvs-commit at gcc dot gnu dot org
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=20050624094716.19808.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).