public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108984] New: [13 Regression] LTO bootstrap causes testsuite ICE
Date: Wed, 01 Mar 2023 10:25:02 +0000 [thread overview]
Message-ID: <bug-108984-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108984
Bug ID: 108984
Summary: [13 Regression] LTO bootstrap causes testsuite ICE
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
I'm seeing the following ICE in a testsuite run after a simple
../configure --with-build-config=bootstrap-lto on x86_64-linux
#0 0x0000000000de94bf in general_operand (op=0x0, mode=E_DImode)
at ../../gcc/gcc/recog.cc:1435
#1 0x00000000018740f9 in nonimmediate_operand (mode=E_DImode, op=0x0)
at ../../gcc/gcc/recog.cc:1720
#2 x86_64_szext_general_operand (mode=E_DImode, op=0x0)
at ../../gcc/gcc/config/i386/predicates.md:505
#3 x86_64_szext_general_operand (op=0x0, mode=E_DImode)
at ../../gcc/gcc/config/i386/predicates.md:503
#4 0x00000000011fcd1d in insn_operand_matches (operand=0x0, opno=2,
icode=CODE_FOR_anddi3) at ../../gcc/gcc/optabs.cc:7793
#5 gen_and2_insn (x=0x7ffff67b9420, y=0x0)
at ../../gcc/gcc/config/i386/i386.cc:8415
#6 0x00000000011fcfb3 in ix86_expand_prologue ()
at ../../gcc/gcc/config/i386/i386.cc:8580
#7 0x00000000011df0fb in gen_prologue ()
at ../../gcc/gcc/config/i386/i386.md:16674
#8 target_gen_prologue () at ../../gcc/gcc/config/i386/i386.md:24241
#9 0x0000000000b504ec in make_prologue_seq ()
at ../../gcc/gcc/function.cc:5841
#10 0x0000000000b60154 in thread_prologue_and_epilogue_insns ()
at ../../gcc/gcc/function.cc:6073
happens when stack_realign_drap, for example for gcc.dg/stack-usage-2.c
next reply other threads:[~2023-03-01 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 10:25 rguenth at gcc dot gnu.org [this message]
2023-03-01 10:44 ` [Bug target/108984] " rguenth at gcc dot gnu.org
2023-03-01 12:14 ` rguenth at gcc dot gnu.org
2023-03-01 12:21 ` jakub at gcc dot gnu.org
2023-03-01 13:05 ` rguenth at gcc dot gnu.org
2023-03-01 13:23 ` rguenth at gcc dot gnu.org
2023-03-01 13:34 ` rguenth at gcc dot gnu.org
2023-03-01 13:45 ` jakub at gcc dot gnu.org
2023-03-01 14:01 ` rguenth at gcc dot gnu.org
2023-03-02 7:25 ` rguenth 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-108984-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).