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: Tue, 04 Feb 2003 22:36:00 -0000 [thread overview] Message-ID: <20030204223601.29108.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> Subject: Re: c++/9265: exception handling faulty wenn linking PIC objects to non PIC ones Date: Tue, 4 Feb 2003 23:28:27 +0100 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 04, 2003 at 03:19:06PM -0500, Jakub Jelinek wrote: > Cannot reproduce this, works just fine with > gcc version 3.2.1 20021207 (Red Hat Linux 8.0 3.2.1-2) > GNU ld version 2.13.90.0.16 20021126 Thanks for checking this. > You obviously cannot mix crt* files between different gcc builds, This is perfectly clear to me. I did this only to track the problem down. 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. I compared SuSE 8.1 to Mandrake 9.0 that have both gcc-3.2, binutils-2.12.90.0.15 and glibc-2.2.5. SuSE has the bug, Mandrake not. So the problem seems to have been introduced by a SuSE specific change to either binutils or glibc. Andreas: This is the reason, why I have put you in CC again. So, from my point of view, we can close this bug here and I will do further discussions about this issue in the SuSE bugzilla. Robert --=20 Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPkA+isQAnns5HcHpAQGx2wf/dIe+eJDSrQlz0Y0U4j7PMJ8Ht9HqxBZm UYy7ujIL530tN1YOidPebdu9oWBpR6Ixjxk/q8UZ6kQpKtSxPPeogYMYJF7c/Yak yB1Ih4gC8heUTD1LeKjWOSP3Jg8rIR44V9puy5uAgqFjJnZeyNrDKr1knkL+6FJR WqeSAApQzDt2QICUQJAPmVOw7LY0MXsTVpNjw7gqZhmAiJemY/F7C9lC1IsSs2V8 5RCvx5orUnbeMkIwXrgZ5cF1gYSZ/e29INojAqNZPOdHkQ+N/zI3h2Bs/ZI3Z4cT 4pecuHJTqZU455nNvNh5UCvqUr2UPTkG1V/hQ3McvlmERRwlqU19Ug== =UFPd -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--
next reply other threads:[~2003-02-04 22:36 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 22:36 Robert Schiele [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-06 9:46 Robert Schiele 2003-02-04 22:40 bangerth 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=20030204223601.29108.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: 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).