public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9265: exception handling faulty wenn linking PIC objects to non PIC ones
Date: Thu, 06 Feb 2003 09:46:00 -0000 [thread overview]
Message-ID: <20030206094600.14337.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9265; it has been noted by GNATS.
From: Robert Schiele <rschiele@uni-mannheim.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: cc@pi3.informatik.uni-mannheim.de, gcc-bugs@gcc.gnu.org,
gcc-gnats@gcc.gnu.org, Andreas Jaeger <aj@suse.de>,
Andreas Schwab <schwab@suse.de>
Subject: Re: c++/9265: exception handling faulty wenn linking PIC objects to non PIC ones
Date: Thu, 6 Feb 2003 10:44:10 +0100
--wq9mPyueHGvFACwf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 04, 2003 at 11:28:27PM +0100, Robert Schiele wrote:
> Now, after I had the first report from someone with recent binutils
> where it was not reproducable, I did some further research and found
> that it seems to be a SuSE specific problem either with the shipped
> glibc or with some vendor patches on binutils.
Ok, it is definitively not a gcc bug, but a binutils bug, but not
invented by SuSE specific patches, but by the fact that they configure
with --enable-targets=3Dx86_64-suse-linux. This seems to break either
ld or libbfd, even on plain binutils 2.12.90.0.15. I haven't yet
tried later releases, but will do so.
If you are interrested in having more information, feel free to
contact me.
Robert
--=20
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
--wq9mPyueHGvFACwf
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iQEVAwUBPkIuacQAnns5HcHpAQG1wgf/d6q7WNIiwENoZpcshL0LcEIPht/94zGr
lHZgSNie8yCImgQcuhNfwImGrabdjqNDPrarnd/eTypbc0ZquO0h2w6NSxG8p7WP
NwWwFCNhfeAqB9pE3pAKeUDasXC4VHKQsmYKLpNw58oAj5wg/0HzD+TKrSEsBlza
5DLndC8acaoCKHIDVDMWrwMswyh0QqjZoLF3GYXNLL6e/JdzUJFqzCa+VjFhS2tz
KIOig5+jiXc+0+0SDwAagL150GRdQYZ5Z4gEEJld1RB6t3aL5kqO+3dtkqEAqNLj
h91OuLo17GRb6A2tFlcnZoe5wNNRwioBtb1rYQI4A4vb+8MLQ+o6hQ==
=6Xsw
-----END PGP SIGNATURE-----
--wq9mPyueHGvFACwf--
next reply other threads:[~2003-02-06 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 9:46 Robert Schiele [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 22:40 bangerth
2003-02-04 22:36 Robert Schiele
2003-02-04 20:26 Jakub Jelinek
2003-02-04 19:46 Robert Schiele
2003-01-14 22:46 Robert Schiele
2003-01-14 9:06 Robert Schiele
2003-01-14 7:06 Robert Schiele
2003-01-13 23:46 Wolfgang Bangerth
2003-01-13 23:36 Robert Schiele
2003-01-13 0:14 bangerth
2003-01-10 18:56 rschiele
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=20030206094600.14337.qmail@sources.redhat.com \
--to=rschiele@uni-mannheim.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).