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/99867] New: [11 Regression] ICE in to_constant, at poly-int.h:504 Date: Thu, 01 Apr 2021 11:37:50 +0000 [thread overview] Message-ID: <bug-99867-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99867 Bug ID: 99867 Summary: [11 Regression] ICE in to_constant, at poly-int.h:504 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: aarch64-linux-gnu gcc-11.0.1-alpha20210328 snapshot (g:499fa254ae8c9752d8c2cf3130b13ffddfd83546) ICEs when compiling gcc/testsuite/gcc.target/aarch64/sve/acle/general/struct_1.c: % aarch64-linux-gnu-gcc-11.0.1 -c gcc/testsuite/gcc.target/aarch64/sve/acle/general/struct_1.c during RTL pass: expand gcc/testsuite/gcc.target/aarch64/sve/acle/general/struct_1.c: In function 'f': gcc/testsuite/gcc.target/aarch64/sve/acle/general/struct_1.c:7:14: internal compiler error: in to_constant, at poly-int.h:504 7 | svint8x2_t x = *a; | ^ 0x6cfe32 poly_int_pod<2u, unsigned short>::to_constant() const /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/poly-int.h:504 0x6d5651 poly_int_pod<2u, unsigned short>::to_constant() const /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/expr.c:3695 0x6d5651 emit_move_multi_word /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/expr.c:3680 0xb450ce emit_move_insn(rtx_def*, rtx_def*) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/expr.c:3936 0xb4d8a7 store_expr(tree_node*, rtx_def*, int, bool, bool) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/expr.c:6072 0xb4f2c0 expand_assignment(tree_node*, tree_node*, bool) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/expr.c:5622 0xa158d7 expand_gimple_stmt_1 /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/cfgexpand.c:3910 0xa158d7 expand_gimple_stmt /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/cfgexpand.c:4008 0xa1bbea expand_gimple_basic_block /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/cfgexpand.c:6045 0xa1d78f execute /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210328/work/gcc-11-20210328/gcc/cfgexpand.c:6729 It does not ICE when provided w/ -march containing "+sve", so I wonder if this PR is really a duplicate of PR99657.
next reply other threads:[~2021-04-01 11:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 11:37 asolokha at gmx dot com [this message] 2021-04-01 12:17 ` [Bug target/99867] " rguenth at gcc dot gnu.org 2021-04-01 15:14 ` [Bug target/99867] [10/11 " acoplan at gcc dot gnu.org 2021-04-08 14:21 ` rguenth at gcc dot gnu.org 2021-11-09 1:12 ` [Bug target/99867] [10/11/12 " 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-99867-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).