public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109359] [12/13 Regression] Compile-time rounding of double literal to float is incorrect with -frounding-math
Date: Fri, 14 Apr 2023 10:03:49 +0000	[thread overview]
Message-ID: <bug-109359-4-1EmFkFQZFm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109359-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ah, cp/constexpr.cc already uses fold_binary_initializer_loc if
-fconstexpr-fp-except.
That will turn the -frounding-math temporarily off for binary operations.
For this PR guess we need to use fold_init or fold_build1_initializer_loc
instead of fold or fold_build1 in the NOP_EXPR handling under the same
conditions.
Plus of course we need to figure out how to fix the issue if we didn't turn
those off (we shouldn't consider the initializer constant then but evaluate
dynamically).

  parent reply	other threads:[~2023-04-14 10:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 12:33 [Bug c++/109359] New: " rcopley at gmail dot com
2023-03-31 13:23 ` [Bug c++/109359] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-03-31 13:36 ` jakub at gcc dot gnu.org
2023-03-31 14:23 ` jakub at gcc dot gnu.org
2023-04-14  9:49 ` rguenth at gcc dot gnu.org
2023-04-14 10:03 ` jakub at gcc dot gnu.org [this message]
2023-04-14 10:08 ` rguenth at gcc dot gnu.org
2023-04-14 10:12 ` jakub at gcc dot gnu.org
2023-05-08 12:26 ` [Bug c++/109359] [12/13/14 " rguenth at gcc dot gnu.org
2024-02-05 18:24 ` jason at gcc dot gnu.org
2024-02-05 18:34 ` [Bug c++/109359] [12/13 " jason at gcc dot gnu.org
2024-02-05 18:47 ` jakub at gcc dot gnu.org
2024-02-05 18:55 ` jason at gcc dot gnu.org
2024-02-05 21:35 ` cvs-commit at gcc dot gnu.org
2024-02-05 22:25 ` cvs-commit at gcc dot gnu.org
2024-02-05 22:25 ` cvs-commit at gcc dot gnu.org
2024-02-05 22:26 ` jason 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-109359-4-1EmFkFQZFm@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).