public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/105235] [11/12 Regression] ICE: in redirect_eh_edge_1, at tree-eh.cc:2323 with custom flags since r11-4519-g53dede0f04bd95c3
Date: Tue, 12 Apr 2022 08:06:37 +0000 [thread overview]
Message-ID: <bug-105235-4-D5INp3gUAn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105235-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105235
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Zdenek Sojka from comment #1)
> A slightly different testcase fails elsewhere:
>
> $ cat testcase.c
> int i, j;
>
> void
> foo (double d)
> {
> i = __builtin_ilogbl (d);
> j = __builtin_sinl (d);
> }
>
> $ x86_64-pc-linux-gnu-gcc -O -fno-tree-dominator-opts -fnon-call-exceptions
> -fsanitize=thread -fno-tree-fre testcase.c
> testcase.c: In function 'foo':
> testcase.c:4:1: error: BB 3 cannot throw but has an EH edge
> 4 | foo (double d)
> | ^~~
> during GIMPLE pass: sincos
> testcase.c:4:1: internal compiler error: verify_flow_info failed
> 0xe7c00e verify_flow_info()
> /repo/gcc-trunk/gcc/cfghooks.cc:284
> 0x128704a execute_function_todo
> /repo/gcc-trunk/gcc/passes.cc:2097
> 0x128755e execute_todo
> /repo/gcc-trunk/gcc/passes.cc:2139
> Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> Please include the complete backtrace with any bug report.
> See <https://gcc.gnu.org/bugs/> for instructions.
Testing a patch for this
next prev parent reply other threads:[~2022-04-12 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 4:06 [Bug sanitizer/105235] New: [12 Regression] ICE: in redirect_eh_edge_1, at tree-eh.cc:2323 with custom flags zsojka at seznam dot cz
2022-04-12 4:07 ` [Bug sanitizer/105235] " zsojka at seznam dot cz
2022-04-12 6:58 ` [Bug sanitizer/105235] [11/12 Regression] ICE: in redirect_eh_edge_1, at tree-eh.cc:2323 with custom flags since r11-4519-g53dede0f04bd95c3 marxin at gcc dot gnu.org
2022-04-12 7:11 ` zsojka at seznam dot cz
2022-04-12 7:20 ` marxin at gcc dot gnu.org
2022-04-12 8:06 ` rguenth at gcc dot gnu.org [this message]
2022-04-12 8:06 ` rguenth at gcc dot gnu.org
2022-04-12 8:07 ` jakub at gcc dot gnu.org
2022-04-12 8:11 ` [Bug tree-optimization/105235] " rguenth at gcc dot gnu.org
2022-04-12 8:11 ` rguenth at gcc dot gnu.org
2022-04-12 9:48 ` cvs-commit at gcc dot gnu.org
2022-04-12 10:49 ` [Bug tree-optimization/105235] [11 " cvs-commit at gcc dot gnu.org
2022-04-12 10:49 ` 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-105235-4-D5INp3gUAn@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).