public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113229] [14 Regression] gcc.dg/torture/pr70083.c ICEs when compiled with -march=armv9-a+sve2
Date: Fri, 05 Jan 2024 22:23:41 +0000 [thread overview]
Message-ID: <bug-113229-4-j2g6dbptgn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113229-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113229
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to avieira from comment #6)
> Oh forgot to mention, this is triggering because of the div optimization in:
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;
> h=c69db3ef7f7d82a50f46038aa5457b7c8cc2d643
>
> But I suspect that too is just an enabler and not the root cause? Unless we
> aren't supposed to use subregs for sve modes...
Note there is another paths which lead to crashing in paradoxical_subreg_p
still via simplify_const_vector_subreg (but not with the gen_divv4si3 in the
trace) in a different testcase; testsuite/gcc.dg/pr69896.c .
```
/home/apinski/src/upstream-full-cross/gcc/gcc/testsuite/gcc.dg/pr69896.c:22:1:
internal compiler error: in paradoxical_subreg_p, at rtl.h:3213
0x80c65b paradoxical_subreg_p(machine_mode, machine_mode)
../../gcc/rtl.h:3213
0x80cfc8 paradoxical_subreg_p(machine_mode, machine_mode)
../../gcc/poly-int.h:2179
0x80cfc8 simplify_const_vector_subreg
../../gcc/simplify-rtx.cc:7423
0x80cfc8 simplify_context::simplify_subreg(machine_mode, rtx_def*,
machine_mode, poly_int<2u, unsigned long>)
../../gcc/simplify-rtx.cc:7595
0xfae1c9 insn_propagation::apply_to_rvalue_1(rtx_def**)
../../gcc/recog.cc:1176
0xfadcab insn_propagation::apply_to_rvalue_1(rtx_def**)
../../gcc/recog.cc:1117
0xfade93 insn_propagation::apply_to_rvalue_1(rtx_def**)
../../gcc/recog.cc:1254
0xfae63f insn_propagation::apply_to_pattern(rtx_def**)
../../gcc/recog.cc:1396
0x1cfdb66 try_fwprop_subst_pattern
../../gcc/fwprop.cc:440
0x1cfdb66 try_fwprop_subst
../../gcc/fwprop.cc:613
0x1cfe500 forward_propagate_and_simplify
../../gcc/fwprop.cc:809
0x1cfe500 forward_propagate_into
../../gcc/fwprop.cc:872
0x1cfe89d forward_propagate_into
../../gcc/fwprop.cc:821
0x1cfe89d fwprop_insn
../../gcc/fwprop.cc:929
0x1cfe9c1 fwprop
../../gcc/fwprop.cc:981
```
next prev parent reply other threads:[~2024-01-05 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 8:20 [Bug target/113229] New: " pinskia at gcc dot gnu.org
2024-01-04 8:21 ` [Bug target/113229] " pinskia at gcc dot gnu.org
2024-01-04 8:25 ` pinskia at gcc dot gnu.org
2024-01-04 8:37 ` pinskia at gcc dot gnu.org
2024-01-05 17:21 ` avieira at gcc dot gnu.org
2024-01-05 17:23 ` avieira at gcc dot gnu.org
2024-01-05 17:23 ` avieira at gcc dot gnu.org
2024-01-05 22:23 ` pinskia at gcc dot gnu.org [this message]
2024-01-08 14:47 ` rguenth at gcc dot gnu.org
2024-01-10 8:01 ` pinskia 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-113229-4-j2g6dbptgn@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: link
Be 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).