public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23602] [4.1 regression] 1081 test failures in libjava, when configured for i486-linux
Date: Sat, 21 Jan 2006 02:11:00 -0000	[thread overview]
Message-ID: <20060121021132.19315.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23602-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from aoliva at gcc dot gnu dot org  2006-01-21 02:11 -------
Created an attachment (id=10694)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10694&action=view)
Reduced testcase

This reduced testcase triggers the same bug before Richard's patch if compiled
with -fasynchronous-unwind-tables, generating very similar code to what broke
the unwinder in the libjava.lang ArrayTest on i486.  With current trunk, even
after reverting the patch, both the reduced testcase and the Java tests all
pass on an i486-pc-linux-gnu native toolchain.  Even though the generated code
is not significantly different, the EH tables are.  I can't tell immediately
whether the problem is actually fixed, and we could thus remove the patch that
hid the problem before, or if it's just more difficult to trigger now.


-- 


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


  parent reply	other threads:[~2006-01-21  2:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23602-5724@http.gcc.gnu.org/bugzilla/>
2005-10-05 18:19 ` cvs-commit at gcc dot gnu dot org
2005-10-05 18:23 ` rth at gcc dot gnu dot org
2006-01-21  2:11 ` aoliva at gcc dot gnu dot org [this message]
2006-03-17  6:25 ` aoliva at gcc dot gnu dot org
2005-08-28 16:41 [Bug target/23602] New: " debian-gcc at lists dot debian dot org
2005-08-28 17:20 ` [Bug target/23602] " debian-gcc at lists dot debian dot org
2005-08-28 21:58 ` pinskia at gcc dot gnu dot org
2005-08-29 21:08 ` debian-gcc at lists dot debian dot org
2005-08-30  2:46 ` rth at gcc dot gnu dot org
2005-08-30  6:00 ` rth at gcc dot gnu dot org
2005-08-30  7:33 ` debian-gcc at lists dot debian dot org
2005-08-31 10:17 ` debian-gcc at lists dot debian dot org
2005-08-31 14:12 ` debian-gcc at lists dot debian dot org
2005-09-02 21:39 ` rth at gcc dot gnu dot org
2005-09-02 21:46 ` tromey at gcc dot gnu dot org
2005-09-02 22:09 ` rth at gcc dot gnu dot org
2005-09-02 22:21 ` debian-gcc at lists dot debian dot org
2005-09-05 13:26 ` debian-gcc at lists dot debian dot org
2005-09-26 13:23 ` debian-gcc at lists dot debian 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=20060121021132.19315.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).