public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42850] [4.5 Regression] FAIL: g++.dg/abi/forced.C execution test
Date: Sun, 31 Jan 2010 17:23:00 -0000 [thread overview]
Message-ID: <20100131172321.24620.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42850-276@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from dave at hiauly1 dot hia dot nrc dot ca 2010-01-31 17:23 -------
Subject: Re: [4.5 Regression] FAIL: g++.dg/abi/forced.C execution test
> (In reply to comment #3)
> > The failure was introduced by my change to the libgcc_s so version.
>
> I always wondered why we have to do this all the time for hppa... every
> other target seems to get along fine without doing this. Considering that
> hppa is dead it's even more disturbing that we have this instability.
The change in signal frame handling for Ada broke some Java applications.
The Java exception support compensated for the signal frame bug.
I wasn't aware of the implicit dependence of glibc on libgcc_s. ldd
doesn't show the dependency.
I think the mininimal change is to back out the version bump, and to
backport the signal frame changes to active GCC versions so that it's
possible to have a consistent set of libraries.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42850
next prev parent reply other threads:[~2010-01-31 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 14:22 [Bug target/42850] New: " danglin at gcc dot gnu dot org
2010-01-23 15:26 ` [Bug target/42850] " rguenth at gcc dot gnu dot org
2010-01-24 15:04 ` dave at hiauly1 dot hia dot nrc dot ca
2010-01-31 16:32 ` danglin at gcc dot gnu dot org
2010-01-31 16:54 ` carlos at systemhalted dot org
2010-01-31 17:06 ` rguenth at gcc dot gnu dot org
2010-01-31 17:23 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2010-01-31 17:26 ` dave at hiauly1 dot hia dot nrc dot ca
2010-01-31 19:38 ` danglin at gcc dot gnu dot org
2010-01-31 19:40 ` danglin 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=20100131172321.24620.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).