This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/42850] [4.5 Regression] FAIL: g++.dg/abi/forced.C execution test
- From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Jan 2010 17:23:21 -0000
- Subject: [Bug target/42850] [4.5 Regression] FAIL: g++.dg/abi/forced.C execution test
- References: <bug-42850-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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