public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105394] New: [12 Regression] ICE: verify_gimple failed with MVE during GIMPLE pass: veclower2 Date: Tue, 26 Apr 2022 12:23:54 +0000 [thread overview] Message-ID: <bug-105394-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105394 Bug ID: 105394 Summary: [12 Regression] ICE: verify_gimple failed with MVE during GIMPLE pass: veclower2 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following fails: $ ./arm-eabi-gcc -c ~/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C -march=armv8.1-m.main+mve -mfloat-abi=hard -O /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C: In function 'void foo(V*, V*)': /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C:9:1: error: integral result type precision does not match field size of 'bit_field_ref' 9 | foo (V *a, V *b) | ^~~ _40 = BIT_FIELD_REF <_6, 32, 0>; /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C:9:1: error: integral result type precision does not match field size of 'bit_field_ref' _42 = BIT_FIELD_REF <_6, 32, 32>; /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C:9:1: error: integral result type precision does not match field size of 'bit_field_ref' _44 = BIT_FIELD_REF <_6, 32, 64>; /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C:9:1: error: integral result type precision does not match field size of 'bit_field_ref' _46 = BIT_FIELD_REF <_6, 32, 96>; during GIMPLE pass: veclower2 /home/alecop01/toolchain/src/gcc/gcc/testsuite/g++.dg/opt/pr79734.C:9:1: internal compiler error: verify_gimple failed 0x110c388 verify_gimple_in_cfg(function*, bool) /home/alecop01/toolchain/src/gcc/gcc/tree-cfg.cc:5561 0xfa3726 execute_function_todo /home/alecop01/toolchain/src/gcc/gcc/passes.cc:2085 0xfa388e do_per_function /home/alecop01/toolchain/src/gcc/gcc/passes.cc:1688 0xfa3a29 execute_todo /home/alecop01/toolchain/src/gcc/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. Since commit r12-7339-g91224cf625dc90304bb515a0cc602beed48fe3da, the arm build was broken. Commit r12-7356-gfd0ab7c734b04b91653467b94afd48ceca122083 fixes the build, and we start seeing the ICE after this commit. So the triggering commit is in this range.
next reply other threads:[~2022-04-26 12:23 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 12:23 acoplan at gcc dot gnu.org [this message] 2022-04-26 12:40 ` [Bug tree-optimization/105394] " rguenth at gcc dot gnu.org 2022-04-26 12:42 ` acoplan at gcc dot gnu.org 2022-04-26 13:18 ` rguenth at gcc dot gnu.org 2022-04-26 13:19 ` rguenth at gcc dot gnu.org 2022-04-26 13:22 ` [Bug target/105394] " rguenth at gcc dot gnu.org 2022-04-29 9:07 ` [Bug target/105394] [12/13 " rguenth at gcc dot gnu.org 2022-04-29 9:20 ` rguenth at gcc dot gnu.org 2022-04-29 9:57 ` rguenth at gcc dot gnu.org 2022-04-29 9:59 ` acoplan at gcc dot gnu.org 2022-05-03 8:34 ` acoplan at gcc dot gnu.org 2022-05-03 8:49 ` rguenther at suse dot de 2022-05-03 9:19 ` cvs-commit at gcc dot gnu.org 2022-05-03 9:25 ` [Bug target/105394] [12 " rguenth at gcc dot gnu.org 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-06 9:27 ` cvs-commit at gcc dot gnu.org 2022-05-06 9:28 ` 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-105394-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).