public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tim Prince <timothyprince@sbcglobal.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9736: same fp comparison can lead to different results Date: Wed, 19 Feb 2003 14:06:00 -0000 [thread overview] Message-ID: <20030219140601.17413.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9736; it has been noted by GNATS. From: Tim Prince <timothyprince@sbcglobal.net> To: Eric Botcazou <ebotcazou@libertysurf.fr>, Richard Addison-Wood <richard@wetafx.co.nz> Cc: gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9736: same fp comparison can lead to different results Date: Wed, 19 Feb 2003 05:56:06 -0800 On Wednesday 19 February 2003 01:02, Eric Botcazou wrote: > > If the compiler produces valid assembly code that does not > > correctly execute the input source code, that is a compiler bug. > > Sure. But why do you keep using a compilation mode that you know will > generate a faulty executable for your program? I can't say much more than > the GCC manual here: if your program relies on exact IEEE floating-point > semantics to properly work, compile it with -ffloat-store. Otherwise > eliminate the dependencies on the IEEE format. You might consider the options -march=pentium[34] -mfpmath=sse, or changing the precision mode you run in, since you seem to want an alternative to -ffloat-store to achieve those effects. -- Tim Prince
next reply other threads:[~2003-02-19 14:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-19 14:06 Tim Prince [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-05 7:46 ebotcazou 2003-03-05 3:26 Richard Addison-Wood 2003-02-27 7:46 Richard Addison-Wood 2003-02-19 9:06 Eric Botcazou 2003-02-18 22:16 Richard Addison-Wood 2003-02-18 8:04 ebotcazou 2003-02-17 23:16 richard
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=20030219140601.17413.qmail@sources.redhat.com \ --to=timothyprince@sbcglobal.net \ --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).