public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stammark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112337] New: arm: ICE in arm_effective_regno Date: Wed, 01 Nov 2023 15:49:15 +0000 [thread overview] Message-ID: <bug-112337-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337 Bug ID: 112337 Summary: arm: ICE in arm_effective_regno Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: stammark at gcc dot gnu.org Target Milestone: --- Hi all, I found this ICE when compiling CMSIS-NN with latest trunk: ./build-arm-eabi-armv8.1-m.main+mve.fp+fp.dp/install/bin/arm-eabi-gcc -mcpu=cortex-m55 ~/gnu/CMSIS-NN/Source/NNSupportFunctions/arm_nn_depthwise_conv_nt_t_padded_s8.c -I ~/gnu/CMSIS-NN/Include/ -O3 -S during RTL pass: ira /home/stamar01/gnu/CMSIS-NN/Source/NNSupportFunctions/arm_nn_depthwise_conv_nt_t_padded_s8.c: In function 'arm_nn_depthwise_conv_nt_t_padded_s8': /home/stamar01/gnu/CMSIS-NN/Source/NNSupportFunctions/arm_nn_depthwise_conv_nt_t_padded_s8.c:172:1: internal compiler error: in arm_effective_regno, at config/arm/arm.cc:13671 172 | } | ^ 0x1b590f2 arm_effective_regno /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/arm.cc:13671 0x1b5923a mve_vector_mem_operand(machine_mode, rtx_def*, bool) /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/arm.cc:13701 0x23015c2 mve_memory_operand(rtx_def*, machine_mode) /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/predicates.md:39 0x23d79fa recog_235 /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/mve.md:3636 0x241db9c recog_287 /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/neon.md:6161 0x24540af recog_344 /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/mve.md:6390 0x2459355 recog(rtx_def*, rtx_insn*, int*) /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/sync.md:462 0x15663f5 insn_invalid_p(rtx_insn*, bool) /home/stamar01/gnu/v8.X-M/src/gcc/gcc/recog.cc:358 0x15667ad verify_changes(int) /home/stamar01/gnu/v8.X-M/src/gcc/gcc/recog.cc:469 0x1350f89 equiv_can_be_consumed_p /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira-costs.cc:1767 0x13518f0 calculate_equiv_gains /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira-costs.cc:1887 0x1351fbe find_costs_and_classes /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira-costs.cc:2007 0x135404c ira_costs() /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira-costs.cc:2564 0x1347e82 ira_build() /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira-build.cc:3481 0x133d895 ira /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira.cc:5793 0x133e215 execute /home/stamar01/gnu/v8.X-M/src/gcc/gcc/ira.cc:6117 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. opening this up in GDB I see that: #1 0x0000000001b590f3 in arm_effective_regno (op=0x7ffff6e130a8, strict=false) at /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/arm.cc:13671 13671 gcc_assert (REG_P (op)); (gdb) p debug_rtx (op) (mem/f/c:SI (plus:SI (reg/f:SI 103 afp) (const_int 28 [0x1c])) [2 output_bias+0 S4 A32]) And slightly further up: #3 0x00000000023015c3 in mve_memory_operand (op=0x7ffff6e24b70, mode=E_V4SImode) at /home/stamar01/gnu/v8.X-M/src/gcc/gcc/config/arm/predicates.md:39 39 && mve_vector_mem_operand (GET_MODE (op), XEXP (op, 0), (gdb) p debug_rtx (op) (mem:V4SI (post_inc:SI (mem/f/c:SI (plus:SI (reg/f:SI 103 afp) (const_int 28 [0x1c])) [2 output_bias+0 S4 A32])) [0 MEM[(int[4] *)bias_176]+0 S16 A32]) I've started a bisect.
next reply other threads:[~2023-11-01 15:49 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 15:49 stammark at gcc dot gnu.org [this message] 2023-11-02 10:02 ` [Bug target/112337] arm: ICE in arm_effective_regno when compiling for MVE rguenth at gcc dot gnu.org 2023-11-02 15:04 ` stammark at gcc dot gnu.org 2023-11-02 15:05 ` stammark at gcc dot gnu.org 2023-11-02 15:05 ` stammark at gcc dot gnu.org 2023-11-07 16:11 ` saurabh.jha at arm dot com 2023-11-07 16:49 ` pinskia at gcc dot gnu.org 2023-11-07 17:10 ` acoplan at gcc dot gnu.org 2023-11-08 12:41 ` vmakarov at gcc dot gnu.org 2023-11-08 12:50 ` acoplan at gcc dot gnu.org 2023-11-10 16:47 ` cvs-commit at gcc dot gnu.org 2023-11-14 14:41 ` saurabh.jha at arm dot com 2023-11-14 14:50 ` cvs-commit at gcc dot gnu.org 2024-01-18 13:21 ` adhemerval.zanella at linaro dot org 2024-01-18 18:01 ` clyon at gcc dot gnu.org 2024-01-19 9:12 ` saurabh.jha at arm dot com 2024-02-05 9:30 ` saurabh.jha at arm dot com 2024-03-05 15:27 ` rearnsha at gcc dot gnu.org 2024-03-05 15:29 ` cvs-commit at gcc dot gnu.org 2024-03-05 15:35 ` rearnsha 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-112337-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).