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 inline-asm/69899] gcc ICE on invalid code on x86_64-linux-gnu in "replace_reg"
Date: Sat, 20 Mar 2021 04:12:59 +0000 [thread overview]
Message-ID: <bug-69899-4-SH8kKilQsa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-69899-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69899
--- Comment #5 from Arseny Solokha <asolokha at gmx dot com> ---
I believe practically all gcc branches, the current gcc-11.0.1-alpha20210314
snapshot (g:c2d7c39fcb8a3cb67600cdb6fde49ecb0e951589) included, demonstrate the
same issue on
gcc/testsuite/gcc.target/s390/vector/long-double-asm-commutative.c w/ -O1
-ffinite-math-only:
% x86_64-unknown-linux-gnu-gcc-11.0.1 -O1 -ffinite-math-only -c
gcc/testsuite/gcc.target/s390/vector/long-double-asm-commutative.c
gcc/testsuite/gcc.target/s390/vector/long-double-asm-commutative.c: In function
'main':
gcc/testsuite/gcc.target/s390/vector/long-double-asm-commutative.c:11:3: error:
output constraint 0 must specify a single register
11 | asm("lxr\t%0,%1\n"
| ^~~
during RTL pass: stack
gcc/testsuite/gcc.target/s390/vector/long-double-asm-commutative.c:16:1:
internal compiler error: in replace_reg, at reg-stack.c:714
16 | }
| ^
0x6b654d replace_reg
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:714
0xd6e91b compare_for_stack_reg
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:1379
0xd6e91b subst_stack_regs_pat
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:2001
0xd6f212 subst_stack_regs
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:2444
0xd6f418 convert_regs_1
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3080
0xd6f418 convert_regs_2
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3214
0xd704c8 convert_regs
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3249
0xd704c8 reg_to_stack
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3374
0xd704c8 rest_of_handle_stack_regs
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3429
0xd704c8 execute
/var/tmp/portage/sys-devel/gcc-11.0.1_alpha20210314/work/gcc-11-20210314/gcc/reg-stack.c:3461
next prev parent reply other threads:[~2021-03-20 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-69899-4@http.gcc.gnu.org/bugzilla/>
2018-12-08 6:29 ` asolokha at gmx dot com
2020-12-02 17:06 ` gscfq@t-online.de
2021-03-20 4:12 ` asolokha at gmx dot com [this message]
2021-05-31 6:13 ` pinskia at gcc dot gnu.org
2021-12-29 0:58 ` [Bug target/69899] " 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-69899-4-SH8kKilQsa@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).