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 07:06:00 -0000 [thread overview] Message-ID: <20030114070601.9840.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 08:03:01 +0100 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 13, 2003 at 05:36:53PM -0600, Wolfgang Bangerth wrote: >=20 > > Wolfgang could you send me the crtbegin.o files from the compilers > > that you tried? >=20 > Attached is the crtbegin.o from the gcc3.2.2 snapshot (2002-12-13) I use,= =20 > compiled on the SuSE machine. This should be closest to your=20 > configuration. 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. Robert --=20 Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPiO2JMQAnns5HcHpAQF2lggArq3QA+qoGTiXdMWasIqbuwI5VeSGgnqs fE8IEoWucvjixIN5XWuo47EV3c6G8K8/zH5oX698ynCmt76ecAkQgPPVJsK0rTQ9 xF/VZVtQEhyb3tyXgwvpIbiczB+fdTwzqYltqmk3Xzx87GUS95uGSSIxxMfIYkYC 3oWzhibp4cQlrrfEylZEOrcIBwl9qs/dbpBv/0mg3T/8BvNliY8q0ucS4Y/rvWRj boaOWKzUVhS6eeqT6Shhd+eEV0oZjYs6HvTNjuzPL6lSSmg9FOIrvuGwD0hPKZF/ EtsD2jXxUH1EEbh44/d/yWytZCRPNS7NBc7fBU6J/AwULrb2MWkg/A== =SqDK -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--
next reply other threads:[~2003-01-14 7:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-14 7: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 9: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=20030114070601.9840.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).