public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Date: Wed, 12 Feb 2003 17:06:00 -0000 [thread overview] Message-ID: <20030212170600.28045.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9052; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: Eric Botcazou <ebotcazou@libertysurf.fr> Cc: Richard.Earnshaw@arm.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, phama@webjockey.net Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Date: 12 Feb 2003 18:01:20 +0100 Op wo 12-02-2003, om 17:55 schreef Eric Botcazou: > > Adding -ffloat-store will probably also make the "misbehaviour" go away. > > It does. > > > GCC is almost certainly using the register result from the current > > iteration to compare with the memory result from an earlier iteration. > > Since the register result has excess precision the compare for equality > > fails. That's not a bug, it's just the FP works on the X86. > > > > So in summary, almost certainly "not a bug". > > I fully concur. I think the PR can be closed. > Nice, one more PR gone (still too many to go :-/). How about 8445, 9654? Those are "bugs" that disappear with -ffloat-store, too. Like I said, I don't know enough about floating point numbers... Greetz Steven
next reply other threads:[~2003-02-12 17:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-12 17:06 Steven Bosscher [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-18 10:41 ebotcazou 2003-02-14 21:16 Toon Moene 2003-02-13 21:56 Eric Botcazou 2003-02-13 19:46 Toon Moene 2003-02-13 11:56 Eric Botcazou 2003-02-12 16:56 Eric Botcazou 2003-02-12 16:46 Richard Earnshaw 2003-02-12 16:36 Steven Bosscher 2003-02-12 16:26 Richard Earnshaw 2003-02-12 15:26 Steven Bosscher 2002-12-24 5:36 phma
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=20030212170600.28045.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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).