public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98914] New: [11 Regression] ICE in rs6000_expand_vector_set, at config/rs6000/rs6000.c:7198
Date: Mon, 01 Feb 2021 11:31:20 +0000 [thread overview]
Message-ID: <bug-98914-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98914
Bug ID: 98914
Summary: [11 Regression] ICE in rs6000_expand_vector_set, at
config/rs6000/rs6000.c:7198
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: powerpc-*-linux-gnu
gcc-11.0.0-alpha20210131 snapshot (g:98342bdd2b7085c9e7e4c9fbb07c3917a0013515)
ICEs when compiling the following testcase, reduced from
gcc/testsuite/gcc.target/powerpc/pr79251-run.p8.c, w/ -mvsx -Og:
void
foo (int __attribute__ ((altivec (vector__))) v)
{
for (int k = 0; k < 1; ++k)
v[k] = 0;
}
% powerpc-e300c3-linux-gnu-gcc-11.0.0 -mvsx -Og -c yo6irbnt.c
during RTL pass: expand
yo6irbnt.c: In function 'foo':
yo6irbnt.c:5:10: internal compiler error: in rs6000_expand_vector_set, at
config/rs6000/rs6000.c:7198
5 | v[k] = 0;
| ~~~~~^~~
0x731be0 rs6000_expand_vector_set(rtx_def*, rtx_def*, rtx_def*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/config/rs6000/rs6000.c:7198
0x157be60 ???
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/config/rs6000/vector.md:1251
0xceb038 maybe_expand_insn(insn_code, unsigned int, expand_operand*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/optabs.c:7820
0xb83bfd expand_vec_set_optab_fn
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/internal-fn.c:2871
0xb83bfd expand_VEC_SET
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/internal-fn.def:148
0x954357 expand_call_stmt
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/cfgexpand.c:2748
0x954357 expand_gimple_stmt_1
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/cfgexpand.c:3843
0x954357 expand_gimple_stmt
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/cfgexpand.c:4007
0x95a01a expand_gimple_basic_block
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/cfgexpand.c:6044
0x95bb5f execute
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210131/work/gcc-11-20210131/gcc/cfgexpand.c:6728
next reply other threads:[~2021-02-01 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:31 asolokha at gmx dot com [this message]
2021-02-02 8:12 ` [Bug target/98914] " rguenth at gcc dot gnu.org
2021-02-03 3:59 ` luoxhu at gcc dot gnu.org
2021-02-03 8:11 ` rguenth at gcc dot gnu.org
2021-02-03 8:15 ` jakub at gcc dot gnu.org
2021-02-04 0:38 ` luoxhu at gcc dot gnu.org
2021-03-22 2:15 ` cvs-commit at gcc dot gnu.org
2021-03-22 2:16 ` luoxhu 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-98914-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: 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).