public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Zahira.Ammarguellat at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111759] New: __FLT_HAS_INFINITY__ has value 1 even when -ffinite-math-only is used.
Date: Tue, 10 Oct 2023 13:44:49 +0000	[thread overview]
Message-ID: <bug-111759-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111759
           Summary: __FLT_HAS_INFINITY__ has value 1 even when
                    -ffinite-math-only is used.
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Zahira.Ammarguellat at intel dot com
  Target Milestone: ---

Not sure if this is a bug but would like community feedback. 

In https://godbolt.org/z/fqMdqfM7n we see that __FLT_HAS_INFINITY__ is set to 1
even when -ffast-math and -ffinite-math-only are used. Shouldn't this be set to
0 in presence of these options?

In limits header:
static _GLIBCXX_USE_CONSTEXPR bool has_infinity = __FLT_HAS_INFINITY__;

That means the value of std::numeric_limits<float>::has_infinity will always be
1 even with -ffast-math and -ffinite-math-only. See
https://godbolt.org/z/M6W6Ejc7W

Is this acceptable?

Any feedback appreciated.
Thanks.

             reply	other threads:[~2023-10-10 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 13:44 Zahira.Ammarguellat at intel dot com [this message]
2023-10-10 13:54 ` [Bug c++/111759] " pinskia at gcc dot gnu.org
2023-10-10 13:58 ` pinskia 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-111759-4@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).