public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114347] wrong constant folding when casting __bf16 to int Date: Fri, 15 Mar 2024 16:58:45 +0000 [thread overview] Message-ID: <bug-114347-4-TIJBeTHvuI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114347-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114347 --- Comment #4 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- I think it's correct that conversions (explicit or implicit) from a value with excess precision convert only once; they don't first remove excess range and precision and then convert to the target type. This is not an assertion about whether we should implement __bf16 with excess precision, though it probably makes sense to do so in general for formats for which processors don't provide direct arithmetic support.
next prev parent reply other threads:[~2024-03-15 16:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-15 4:55 [Bug c/114347] New: " eggert at cs dot ucla.edu 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 [this message] 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-TIJBeTHvuI@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).