public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108742] Incorrect constant folding with (or exposed by) -fexcess-precision=standard
Date: Thu, 09 Feb 2023 17:26:29 +0000	[thread overview]
Message-ID: <bug-108742-4-ipvM85HqaV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108742-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
As discussed, FLT_EVAL_METHOD applies to constants as well as to 
operations.  See the example in C17 F.8.5, for example; it shows

float y = 1.1e75f; // may raise exceptions

since 1.1e75f may be evaluated to a wider range and precision than those 
of float, in which case the conversion to the range and precision of float 
occurs at runtime (whereas if there is no excess range and precision for 
float, the constant is evaluated to positive infinity of type float at 
translation time).

  parent reply	other threads:[~2023-02-09 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:50 [Bug middle-end/108742] New: " matz at gcc dot gnu.org
2023-02-09 15:56 ` [Bug middle-end/108742] " marxin at gcc dot gnu.org
2023-02-09 16:06 ` [Bug target/108742] " jakub at gcc dot gnu.org
2023-02-09 16:10 ` jakub at gcc dot gnu.org
2023-02-09 16:19 ` matz at gcc dot gnu.org
2023-02-09 16:25 ` jakub at gcc dot gnu.org
2023-02-09 16:31 ` jakub at gcc dot gnu.org
2023-02-09 16:34 ` jakub at gcc dot gnu.org
2023-02-09 16:52 ` matz at gcc dot gnu.org
2023-02-09 17:00 ` matz at gcc dot gnu.org
2023-02-09 17:01 ` jakub at gcc dot gnu.org
2023-02-09 17:13 ` matz at gcc dot gnu.org
2023-02-09 17:26 ` joseph at codesourcery dot com [this message]
2023-06-29  8:04 ` pinskia at gcc dot gnu.org
2023-06-29 10:59 ` pdimov at gmail dot com
2023-06-30  7:28 ` mkretz at gcc dot gnu.org
2023-06-30  7:36 ` 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-108742-4-ipvM85HqaV@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).