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 tree-optimization/104450] [12 Regression] ICE: verify_flow_info failed: BB 2 cannot throw but has an EH edge with -O -fnon-call-exceptions -fsanitize=thread -mavx512f Date: Tue, 08 Feb 2022 21:14:09 +0000 [thread overview] Message-ID: <bug-104450-4-YE6BLB08ua@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104450 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-02-08 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase without -fsanitize=thread: That is you just need -O1 -fnon-call-exceptions -mavx512f: #define vectsize 64 typedef int __attribute__((__vector_size__ (vectsize))) V; typedef float __attribute__((__vector_size__ (vectsize))) F; F f; V v; struct g{~g();}; void foo (void) { g t; v += (V) (0 <= f); } ----- CUT ---- We start out with (the comparison throws): f.0_1 = f; _6 = f.0_1 >= { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0 }; <bb 3> [local count: 1073741824]: _2 = VEC_COND_EXPR <_6, { -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1 }, { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }>; v.1_3 = v; And isel converts it into: f.0_1 = f; <bb 3> [local count: 1073741824]: _2 = .VCOND (f.0_1, { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0 }, { -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1 }, { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, 111); But now the comparison and VEC_COND_EXPR is just the builtin .VCOND which is not marked to throw and in bb3 ....
next prev parent reply other threads:[~2022-02-08 21:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 20:21 [Bug middle-end/104450] New: " zsojka at seznam dot cz 2022-02-08 21:07 ` [Bug tree-optimization/104450] " pinskia at gcc dot gnu.org 2022-02-08 21:14 ` pinskia at gcc dot gnu.org [this message] 2022-02-09 0:28 ` [Bug tree-optimization/104450] [11/12 " pinskia at gcc dot gnu.org 2022-02-09 7:41 ` rguenth at gcc dot gnu.org 2022-02-09 9:07 ` cvs-commit at gcc dot gnu.org 2022-03-28 11:06 ` [Bug tree-optimization/104450] [11 " marxin at gcc dot gnu.org 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2023-04-17 10:44 ` cvs-commit at gcc dot gnu.org 2023-04-17 10:46 ` rguenth 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-104450-4-YE6BLB08ua@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).