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/103097] New: ICE in move_for_stack_reg, at reg-stack.c:1186
Date: Fri, 05 Nov 2021 11:06:59 +0000 [thread overview]
Message-ID: <bug-103097-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103097
Bug ID: 103097
Summary: ICE in move_for_stack_reg, at reg-stack.c:1186
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: error-recovery, ice-on-invalid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: x86_64-unknown-linux-gnu
gcc-12.0.0-alpha20211031 snapshot (g:ca84f39399fda80c770306465276ffd66d3766ed)
ICEs when compiling
gcc/testsuite/gcc.target/s390/vector/long-double-asm-earlyclobber.c w/ -O1
-fharden-conditional-branches:
% x86_64-unknown-linux-gnu-gcc-12.0.0 -O1 -fharden-conditional-branches -c
gcc/testsuite/gcc.target/s390/vector/long-double-asm-earlyclobber.c
gcc/testsuite/gcc.target/s390/vector/long-double-asm-earlyclobber.c: In
function 'main':
gcc/testsuite/gcc.target/s390/vector/long-double-asm-earlyclobber.c:12:3:
error: output constraint 0 must specify a single register
12 | asm("lzxr\t%0\n"
| ^~~
during RTL pass: stack
gcc/testsuite/gcc.target/s390/vector/long-double-asm-earlyclobber.c:17:1:
internal compiler error: in move_for_stack_reg, at reg-stack.c:1186
17 | }
| ^
0x7077c5 move_for_stack_reg
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:1186
0xe0567a subst_stack_regs
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:2457
0xe05851 convert_regs_1
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3093
0xe05851 convert_regs_2
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3227
0xe069a1 convert_regs
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3262
0xe069a1 reg_to_stack
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3387
0xe069a1 rest_of_handle_stack_regs
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3442
0xe069a1 execute
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/reg-stack.c:3474
next reply other threads:[~2021-11-05 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 11:06 asolokha at gmx dot com [this message]
2021-11-05 11:33 ` [Bug target/103097] " marxin at gcc dot gnu.org
2021-11-19 12:49 ` aoliva at gcc dot gnu.org
2021-12-09 2:39 ` cvs-commit at gcc dot gnu.org
2021-12-09 2:53 ` aoliva 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-103097-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).