public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114347] New: wrong constant folding when casting __bf16 to int Date: Fri, 15 Mar 2024 04:55:48 +0000 [thread overview] Message-ID: <bug-114347-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114347 Bug ID: 114347 Summary: wrong constant folding when casting __bf16 to int Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: eggert at cs dot ucla.edu Target Milestone: --- This is gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6) on Fedora 39. I found this bug when looking into a GNU coreutils report <https://bugs.gnu.org/69770> originally reported against Clang (Clang has a different bug). Compile and run this program: __bf16 x = 257.0bf16; int main (void) { return (int) x != (int) 257.0bf16; } with "gcc -O2 v.c; ./a.out; echo $?". This prints "1"; it should print "0". The problem is that GCC constant-folds '(int) 257.0bf16' to 257. This is incorrect, as 257.0bf16 is exactly equal to 256.0bf16, due to rounding when the constant is parsed. The expression '(int) x' correctly yields 256 at runtime, and 256 is not equal to the 257 incorrectly yielded by the constant folding.
next reply other threads:[~2024-03-15 4:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-15 4:55 eggert at cs dot ucla.edu [this message] 2024-03-15 5:01 ` [Bug middle-end/114347] " pinskia at gcc dot gnu.org 2024-03-15 5:19 ` eggert at cs dot ucla.edu 2024-03-15 9:03 ` rguenth at gcc dot gnu.org 2024-03-15 16:58 ` jsm28 at gcc dot gnu.org 2024-03-18 8:03 ` rguenth at gcc dot gnu.org 2024-03-18 8:16 ` jakub at gcc dot gnu.org 2024-03-18 8:53 ` rguenth at gcc dot gnu.org 2024-03-18 9:06 ` jakub at gcc dot gnu.org 2024-03-18 9:08 ` liuhongt at gcc dot gnu.org 2024-03-20 6:02 ` eggert at cs dot ucla.edu 2024-03-20 6:19 ` pinskia at gcc dot gnu.org 2024-03-21 0:48 ` cvs-commit at gcc dot gnu.org 2024-03-25 22: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-114347-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: linkBe 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).