public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104427] ICE with __builtin_assoc_barrier and float types which introduce excess precision Date: Mon, 07 Feb 2022 18:53:12 +0000 [thread overview] Message-ID: <bug-104427-4-jsaiB7g8Rc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104427-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104427 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ICE with |ICE with |__builtin_assoc_barrier and |__builtin_assoc_barrier and |float16 types |float types which introduce | |excess precision Target| |aarch64*-* x86_64-*-* --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- It is an interaction between excess_precision_expr and the barrier. Here is another testcase which shows the same issue but on i?86 (-m32 -mno-sse -std=c99): float x, y; int foo() { return __builtin_assoc_barrier(x + y) - y; }
next prev parent reply other threads:[~2022-02-07 18:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 18:44 [Bug c/104427] New: [12 Regression] ICE in gimplify_expr, at gimplify.cc:15759 gscfq@t-online.de 2022-02-07 18:49 ` [Bug c/104427] ICE with __builtin_assoc_barrier and float16 types pinskia at gcc dot gnu.org 2022-02-07 18:53 ` pinskia at gcc dot gnu.org [this message] 2022-02-07 18:53 ` [Bug c/104427] ICE with __builtin_assoc_barrier and float types which introduce excess precision pinskia at gcc dot gnu.org 2022-02-08 9:04 ` rguenth at gcc dot gnu.org 2022-02-08 9:19 ` mkretz at gcc dot gnu.org 2022-02-08 9:29 ` rguenth at gcc dot gnu.org 2022-02-08 12:12 ` jakub at gcc dot gnu.org 2022-02-09 19:46 ` cvs-commit at gcc dot gnu.org 2024-01-26 6:59 ` 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-104427-4-jsaiB7g8Rc@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).