public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94111] Wrong constant folding: decimal floating-point infinity casted to double -> zero
Date: Tue, 10 Mar 2020 09:47:57 +0000	[thread overview]
Message-ID: <bug-94111-4-OBcFUZM4Zc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94111-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94111

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |rguenth at gcc dot gnu.org
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2020-03-10
     Ever confirmed|0                           |1
            Summary|Wrong optimization: decimal |Wrong constant folding:
                   |floating-point infinity     |decimal floating-point
                   |casted to double -> zero    |infinity casted to double
                   |                            |-> zero

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This goes wrong somewhere in constant folding:

  d.1_2 = d_13;
  _3 = (double) d.1_2;

 ->

  d.1_2 =  Inf;
  _3 = 0.0;

so (double) Inf is computed wrong.

  reply	other threads:[~2020-03-10  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 21:07 [Bug middle-end/94111] New: Wrong optimization: " ch3root at openwall dot com
2020-03-10  9:47 ` rguenth at gcc dot gnu.org [this message]
2020-03-10  9:58 ` [Bug middle-end/94111] Wrong constant folding: " jakub at gcc dot gnu.org
2020-03-10 10:00 ` jakub at gcc dot gnu.org
2020-03-10 11:48 ` jakub at gcc dot gnu.org
2020-03-11  8:37 ` jakub at gcc dot gnu.org
2020-03-17 18:57 ` cvs-commit at gcc dot gnu.org
2020-09-17 14:24 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:16 ` jakub at gcc dot gnu.org

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=bug-94111-4-OBcFUZM4Zc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).