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/105374] New: [12 Regression] ICE in fold_convert_loc, at fold-const.cc:2580 during GIMPLE pass: reassoc since r12-7338-g884f77b4222289510e1df9db2889b60c5df6fcda Date: Mon, 25 Apr 2022 12:08:17 +0000 [thread overview] Message-ID: <bug-105374-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105374 Bug ID: 105374 Summary: [12 Regression] ICE in fold_convert_loc, at fold-const.cc:2580 during GIMPLE pass: reassoc since r12-7338-g884f77b4222289510e1df9db2889b60c5df6fcda 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: $ cat t.cc typedef float v4f __attribute__((vector_size(4 * sizeof(float)))); v4f f_x, f_y; long f() { return (f_x < f_y | f_x <= f_y)[2]; } $ ./arm-eabi-gcc -c t.cc -march=armv8.1-m.main+mve -mfloat-abi=hard -O during GIMPLE pass: reassoc t.cc: In function 'long int f()': t.cc:3:6: internal compiler error: in fold_convert_loc, at fold-const.cc:2580 3 | long f() { return (f_x < f_y | f_x <= f_y)[2]; } | ^ 0xcb5136 fold_convert_loc(unsigned int, tree_node*, tree_node*) /home/alecop01/toolchain/src/gcc/gcc/fold-const.cc:2580 0x12ef522 eliminate_redundant_comparison /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:2257 0x12ef522 optimize_ops_list /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:2448 0x12f5a0b reassociate_bb /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:6737 0x12f8496 reassociate_bb /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:6899 0x12f8929 do_reassoc /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:7011 0x12f8929 execute_reassoc /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:7100 0x12f8929 execute /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-reassoc.cc:7141 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. Bisection shows the issue started with r12-7338-g884f77b4222289510e1df9db2889b60c5df6fcda : commit 884f77b4222289510e1df9db2889b60c5df6fcda Author: Christophe Lyon <christophe.lyon@arm.com> Date: Wed Oct 13 10:16:22 2021 arm: Implement MVE predicates as vectors of booleans
next reply other threads:[~2022-04-25 12:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 12:08 acoplan at gcc dot gnu.org [this message] 2022-04-25 12:09 ` [Bug tree-optimization/105374] " acoplan at gcc dot gnu.org 2022-04-25 13:43 ` jakub at gcc dot gnu.org 2022-04-25 13:44 ` jakub at gcc dot gnu.org 2022-04-25 13:47 ` jakub at gcc dot gnu.org 2022-04-25 14:27 ` clyon at gcc dot gnu.org 2022-04-25 15:23 ` clyon at gcc dot gnu.org 2022-04-25 16:38 ` marxin at gcc dot gnu.org 2022-04-25 16:39 ` marxin at gcc dot gnu.org 2022-04-26 6:33 ` rguenth at gcc dot gnu.org 2022-04-26 7:58 ` cvs-commit at gcc dot gnu.org 2022-04-26 7:58 ` jakub at gcc dot gnu.org 2022-04-27 8:20 ` cvs-commit 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-105374-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).