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, 14 Jan 2003 09:06:00 -0000 [thread overview] Message-ID: <20030114090602.348.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: Wolfgang Bangerth <bangerth@ticam.utexas.edu> 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, 14 Jan 2003 10:05:00 +0100 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 14, 2003 at 08:03:01AM +0100, Robert Schiele wrote: > Thanks. With your crtbegin.o it also works for me. So I will try to > build a gcc 3.2 with binutils 2.12.x.x.x to check whether it makes a > difference which binutils are used to build the compiler. Well, I got the switch that triggers it: HAVE_LD_EH_FRAME_HDR If this Macro was defined, the crtbegin code cannot handle the situation I described in the bug report. Without it can handle the situation quite sane. This is the case with _all_ compilers since 3.2 release. (I haven't an older one at hand to test.) Obviously this switched is on if you used binutils 2.12.x.x.x at configure time as they support this feature, but 2.11.x.x.x do not and such it is turned off there. So it is perfectly clear now, why you couldn't reproduce the problem. This means the problem obviously is in the crtstuff code that handles eh_frame_hdr stuff. So we need some binutils gurus here. Robert --=20 Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPiPSu8QAnns5HcHpAQF1UQf/cK/bEJaOYPATaPgcsPt/godwCs0tL96O iCjOlCBO1LOQwfrJ5TJ9SHPwNWyHCGCw7Oc5VJESF1/scmT82vhSCOc6VT/9sjrO zK9py1Cj4GHD4z2JqF2MPiL1P/fx1jgY/LdJftl/mz1vnr5tMqhUSej/UumNQlAX j392YqgESPqIDTsuFqIs0IjD0o84IMGvTFRXaySFE6FapbdP0IaDk9F131W1r7aM I4J19r7A63ksSaj5DCuiJe2yoaVRlyDTAt9Z46ncxvCzzBkN1my8sqgdhKbHp8Ti XhWU1uhS8m73kJGvmM+j5Dkx2YL2a/k4XmEQVuVPPKAjojlsZUy6MQ== =Bg1H -----END PGP SIGNATURE----- --wac7ysb48OaltWcw--
next reply other threads:[~2003-01-14 9:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-14 9:06 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 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 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=20030114090602.348.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).