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 target/112906] New: [14 Regression] aarch64: ICE with SVE ACLE code at -O2 Date: Thu, 07 Dec 2023 15:48:06 +0000 [thread overview] Message-ID: <bug-112906-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112906 Bug ID: 112906 Summary: [14 Regression] aarch64: ICE with SVE ACLE code at -O2 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following appears to be a recent regression on the trunk: $ cat t.c #pragma GCC aarch64 "arm_sve.h" int c; long d; void f() { unsigned char *b; svbool_t x = svptrue_b8(); svuint32_t g; svuint8_t h, i; d = 0; for (; (int *)d < &c; d += 16) { h = svld1rq(x, &b[d]); g = svdot_lane(g, i, h, 3); } svst1_vnum(x, &c, 8, g); } $ gcc/xgcc -B gcc -c t.c -O2 -march=armv8.2-a+sve t.c: In function ‘f’: t.c:15:1: error: unrecognizable insn: 15 | } | ^ (insn 55 13 56 3 (set (reg:DI 129) (post_inc:DI (reg:DI 100 [ ivtmp.14 ]))) "t.c":11:9 -1 (expr_list:REG_INC (reg:DI 100 [ ivtmp.14 ]) (nil))) during RTL pass: sched1 t.c:15:1: internal compiler error: in extract_insn, at recog.cc:2812 0x745bc7 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /home/alecop01/toolchain/src/gcc/gcc/rtl-error.cc:108 0x745bfb _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /home/alecop01/toolchain/src/gcc/gcc/rtl-error.cc:116 0xe588cf extract_insn(rtx_insn*) /home/alecop01/toolchain/src/gcc/gcc/recog.cc:2812 0xcbd363 scan_one_insn /home/alecop01/toolchain/src/gcc/gcc/ira-costs.cc:1546 0xcbd363 process_bb_for_costs /home/alecop01/toolchain/src/gcc/gcc/ira-costs.cc:1748 0xcbf607 find_costs_and_classes /home/alecop01/toolchain/src/gcc/gcc/ira-costs.cc:2032 0xcbfeb3 ira_set_pseudo_classes(bool, _IO_FILE*) /home/alecop01/toolchain/src/gcc/gcc/ira-costs.cc:2618 0x1caea5b alloc_global_sched_pressure_data /home/alecop01/toolchain/src/gcc/gcc/haifa-sched.cc:7201 0x1caea5b sched_init() /home/alecop01/toolchain/src/gcc/gcc/haifa-sched.cc:7356 0x1cb041f haifa_sched_init() /home/alecop01/toolchain/src/gcc/gcc/haifa-sched.cc:7368 0xea0c0f schedule_insns() /home/alecop01/toolchain/src/gcc/gcc/sched-rgn.cc:3524 0xea138f schedule_insns() /home/alecop01/toolchain/src/gcc/gcc/sched-rgn.cc:3518 0xea138f rest_of_handle_sched /home/alecop01/toolchain/src/gcc/gcc/sched-rgn.cc:3736 0xea138f execute /home/alecop01/toolchain/src/gcc/gcc/sched-rgn.cc:3846 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.
next reply other threads:[~2023-12-07 15:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-07 15:48 acoplan at gcc dot gnu.org [this message] 2023-12-07 16:08 ` [Bug target/112906] [14 Regression] aarch64: ICE with SVE ACLE code at -O2 since r14-3981-g0f1f6cf87 acoplan at gcc dot gnu.org 2023-12-07 20:42 ` pinskia at gcc dot gnu.org 2023-12-07 22:07 ` acoplan at gcc dot gnu.org 2023-12-14 15:09 ` acoplan at gcc dot gnu.org 2023-12-15 9:36 ` cvs-commit at gcc dot gnu.org 2023-12-15 9:36 ` cvs-commit at gcc dot gnu.org 2023-12-15 9:40 ` acoplan 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-112906-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).