public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org
To: ac@m2000.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/10078: bad code generated with optimisation.
Date: Fri, 14 Mar 2003 11:32:00 -0000	[thread overview]
Message-ID: <20030314113255.15157.qmail@sources.redhat.com> (raw)

Synopsis: bad code generated with optimisation.

State-Changed-From-To: open->closed
State-Changed-By: ebotcazou
State-Changed-When: Fri Mar 14 11:32:55 2003
State-Changed-Why:
    Not a bug. On x86, when optimizing, floating point values
    may be kept in FP registers when doing comparison with
    others stored in memory. Now x86 FP registers have
    extra-precision over a 'double', which may invalid
    an equality comparison. Compile your code with '-ffloat-store'
    if it relies on exact IEEE floating-point semantics.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10078


             reply	other threads:[~2003-03-14 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 11:32 ebotcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-14 10:56 ac

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=20030314113255.15157.qmail@sources.redhat.com \
    --to=ebotcazou@gcc.gnu.org \
    --cc=ac@m2000.fr \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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: link
Be 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).