public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/106726] ICE: verify_gimple failed (dead statement in EH table) on __builtin_alloca_with_align() with -fsanitize=hwaddress -fstack-check=generic -fexceptions Date: Sat, 07 Jan 2023 08:32:54 +0000 [thread overview] Message-ID: <bug-106726-4-zRZKOuyGXs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106726-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106726 --- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> --- This can now be also observed on the x86_64 target, with -mlam=u57: $ x86_64-pc-linux-gnu-gcc -fsanitize=hwaddress -fstack-check=generic -fexceptions -mlam=u57 testcase.c testcase.c: In function 'foo': testcase.c:4:1: error: dead statement in EH table 4 | foo (void) | ^~~ # _4 = VDEF <.MEM_2> _5 = __builtin_alloca_with_align (64, 512); during GIMPLE pass: asan0 testcase.c:4:1: internal compiler error: verify_gimple failed 0x141d106 verify_gimple_in_cfg(function*, bool, bool) /repo/gcc-trunk/gcc/tree-cfg.cc:5647 0x12c0e20 execute_function_todo /repo/gcc-trunk/gcc/passes.cc:2091 0x12c13cb execute_todo /repo/gcc-trunk/gcc/passes.cc:2145 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.
prev parent reply other threads:[~2023-01-07 8:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106726-4@http.gcc.gnu.org/bugzilla/> 2022-08-24 4:52 ` pinskia at gcc dot gnu.org 2022-08-24 8:06 ` marxin at gcc dot gnu.org 2023-01-07 8:32 ` zsojka at seznam dot cz [this message]
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-106726-4-zRZKOuyGXs@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).