public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100217] New: [11/12 Regression] ICE when building valgrind testsuite with -march=z14 since r11-7552
Date: Thu, 22 Apr 2021 18:24:25 +0000 [thread overview]
Message-ID: <bug-100217-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100217
Bug ID: 100217
Summary: [11/12 Regression] ICE when building valgrind
testsuite with -march=z14 since r11-7552
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
The following testcase reduced from valgrind ICEs on s390x with
-mlong-double-128 -march=z14 (with -O2 too):
void
foo (void)
{
register long double f0 asm ("f0");
f0 = 1.0L;
asm("" : : "f" (f0));
}
starting with r11-7552-g3cb8aab390ccf31e4581863b080db30c6735e51e
fpext.i: In function ‘foo’:
fpext.i:6:3: internal compiler error: in gen_rtx_SUBREG, at emit-rtl.c:1023
6 | asm("" : : "f" (f0));
| ^~~
0xcbf9c2 gen_rtx_SUBREG(machine_mode, rtx_def*, poly_int<1u, unsigned long>)
../../gcc/emit-rtl.c:1023
0x1c0a54f gen_tf_to_fprx2(rtx_def*, rtx_def*)
/usr/src/gcc-test/objz2/gcc/insn-emit.c:4851
0x1725bcb s390_md_asm_adjust
../../gcc/config/s390/s390.c:16786
0xb88cf4 expand_asm_stmt
../../gcc/cfgexpand.c:3424
0xb8a308 expand_gimple_stmt_1
../../gcc/cfgexpand.c:3841
0xb8a9af expand_gimple_stmt
../../gcc/cfgexpand.c:4008
0xb92fad expand_gimple_basic_block
../../gcc/cfgexpand.c:6045
0xb94da2 execute
../../gcc/cfgexpand.c:6729
next reply other threads:[~2021-04-22 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 18:24 jakub at gcc dot gnu.org [this message]
2021-04-22 18:25 ` [Bug target/100217] " jakub at gcc dot gnu.org
2021-04-22 18:34 ` jakub at gcc dot gnu.org
2021-04-23 8:22 ` jakub at gcc dot gnu.org
2021-04-23 10:27 ` iii at linux dot ibm.com
2021-04-23 10:31 ` jakub at gcc dot gnu.org
2021-04-23 11:00 ` jakub at gcc dot gnu.org
2021-04-23 11:20 ` iii at linux dot ibm.com
2021-04-23 11:27 ` jakub at gcc dot gnu.org
2021-04-23 11:39 ` jakub at gcc dot gnu.org
2021-04-23 11:56 ` iii at linux dot ibm.com
2021-04-26 14:40 ` iii at linux dot ibm.com
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-04-28 18:22 ` mark at gcc dot gnu.org
2021-04-28 19:14 ` jakub at gcc dot gnu.org
2021-04-29 9:58 ` mark at gcc dot gnu.org
2021-05-03 10:50 ` cvs-commit at gcc dot gnu.org
2021-05-06 1:26 ` cvs-commit at gcc dot gnu.org
2021-06-11 13:43 ` jakub 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-100217-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).