public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107209] New: [13 Regression] ICE: verify_gimple failed (error: statement marked for throw, but doesn't) Date: Tue, 11 Oct 2022 04:29:46 +0000 [thread overview] Message-ID: <bug-107209-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107209 Bug ID: 107209 Summary: [13 Regression] ICE: verify_gimple failed (error: statement marked for throw, but doesn't) Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: aarch64-linux-gnu gcc 13.0.0 20221009 snapshot (g:e95e91eccd022a4a3a86da2749809fbad9afd20e) ICEs when compiling the following testcase, reduced from gcc/testsuite/gcc.target/aarch64/simd/vmulx_f64_2.c, w/ -O2 -fnon-call-exceptions -fno-tree-fre: #include <arm_neon.h> float64x1_t foo (void) { float64_t v1 = 3.14159265359; float64_t v2 = 1.383894; float64_t vec_1_data[] = {v1}; float64_t vec_2_data[] = {v2}; float64x1_t vec_1 = vld1_f64 (vec_1_data); float64x1_t vec_2 = vld1_f64 (vec_2_data); return vmulx_f64 (vec_1, vec_2); } % aarch64-linux-gnu-gcc-13 -O2 -fnon-call-exceptions -fno-tree-fre -c i2myytft.c i2myytft.c: In function 'foo': i2myytft.c:14:1: error: statement marked for throw, but doesn't 14 | } | ^ _24 = 4.34763122374727917218706352286972105503082275390625e+0; during GIMPLE pass: evrp i2myytft.c:14:1: internal compiler error: verify_gimple failed 0xf7ec8d verify_gimple_in_cfg(function*, bool) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/tree-cfg.cc:5648 0xe3af47 execute_function_todo /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/passes.cc:2091 0xe3b47e execute_todo /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221009/work/gcc-13-20221009/gcc/passes.cc:2145
next reply other threads:[~2022-10-11 4:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-11 4:29 asolokha at gmx dot com [this message] 2022-10-11 7:27 ` [Bug tree-optimization/107209] " rguenth at gcc dot gnu.org 2022-10-11 15:57 ` pinskia at gcc dot gnu.org 2022-10-18 8:08 ` rguenth at gcc dot gnu.org 2022-10-18 8:29 ` [Bug target/107209] " rguenth at gcc dot gnu.org 2022-11-30 17:26 ` jakub at gcc dot gnu.org 2022-12-20 9:22 ` ktkachov at gcc dot gnu.org 2022-12-20 9:29 ` jakub at gcc dot gnu.org 2023-01-13 10:01 ` cvs-commit at gcc dot gnu.org 2023-01-13 10:09 ` rsandifo 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-107209-4@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).