public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: ro@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5505: Doubts about a patch for OSF Date: Fri, 22 Feb 2002 14:16:00 -0000 [thread overview] Message-ID: <20020222220601.11578.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5505; it has been noted by GNATS. From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: Richard.Kreckel@Uni-Mainz.DE Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/5505: Doubts about a patch for OSF Date: Fri, 22 Feb 2002 23:04:01 +0100 (MET) Richard B. Kreckel writes: > Err, while trying to debug into the problem I discovered something > that had escaped my attantion until now: compiling CLN and an example > (examples/e, or tests/tests or whatever, never mind) with either -O1, -O2 > or -O1 -g resulted in a working test (the linker warnings are of course > still present) while -O2 -fno-exceptions produced a crashing program. > Also, these funny warnings: > as1: Warning: /tmp/ccb8ZbYD.s, line 6: macro instruction used $at > appear only when I disable exceptions. I hadn't noticed it so far because > I *always* export CXXFLAGS="-O2 -fno-exceptions" prior to building > CLN. May I ask you how you configured and tested CLN? You did not > specify -fno-exceptions, did you? Does it work when you do so? I get those warnings and crashing test programs only when configuring with CXXFLAGS='-fno-exceptions' CPPFLAGS="-DNO_ASM -DNO_PROVIDE_REQUIRE" \ ./configure --disable-shared --without-gmp CXXFLAGS=-fno-exceptions alone still works. > Anyways, here is a g++ -v output as you requested: Thanks, nothing unusual here. Rainer
next reply other threads:[~2002-02-22 22:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-22 14:16 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-10 5:36 Rainer Orth 2002-05-10 5:27 ro 2002-05-09 10:56 Richard B. Kreckel 2002-04-16 10:56 Rainer Orth 2002-02-25 8:58 Rainer Orth 2002-02-23 14:12 Richard B. Kreckel 2002-02-22 15:46 Rainer Orth 2002-02-21 16:21 Richard B. Kreckel 2002-02-20 9:36 Richard B. Kreckel 2002-02-19 5:26 Rainer Orth 2002-02-18 12:56 Richard B. Kreckel 2002-02-04 11:06 Richard B. Kreckel 2002-02-04 11:06 Rainer Orth 2002-01-30 6:14 ro 2002-01-27 6:26 kreckel
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=20020222220601.11578.qmail@sources.redhat.com \ --to=ro@techfak.uni-bielefeld.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=ro@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).