public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109294] Inconsistent exp function implementations for compile time and run time evaluation
Date: Mon, 27 Mar 2023 13:55:09 +0000 [thread overview]
Message-ID: <bug-109294-4-QiPM4mlvx5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109294-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109294
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Dávid Péter Jánosa from comment #0)
> Based on the calls, the same binary will provide different results for use
> case 1 vs 3 which is a bug.
> Also, the result will be different for use case 2 in -O0 and -O3, which is
> also a bug.
No, those are not bugs, see the discussion in
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p1383r1.pdf
It's not reasonable to expect the exact same results for floating-point maths
under all conditions.
next prev parent reply other threads:[~2023-03-27 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:54 [Bug c++/109294] New: " jdavidpeter at gmail dot com
2023-03-27 13:38 ` [Bug c++/109294] " xry111 at gcc dot gnu.org
2023-03-27 13:55 ` redi at gcc dot gnu.org [this message]
2023-03-27 15:21 ` 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-109294-4-QiPM4mlvx5@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).