public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/101157] New: [12 regression] ICE compiling gcc.target/powerpc/stack-limit.c after r12-1702
Date: Mon, 21 Jun 2021 20:33:23 +0000 [thread overview]
Message-ID: <bug-101157-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101157
Bug ID: 101157
Summary: [12 regression] ICE compiling
gcc.target/powerpc/stack-limit.c after r12-1702
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:7232f7c4c2d727431096a7ecfcf4ad4db71dcf2a, r12-1702
make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/stack-limit.c"
FAIL: gcc.target/powerpc/stack-limit.c (internal compiler error)
FAIL: gcc.target/powerpc/stack-limit.c (test for excess errors)
# of unexpected failures 2
I saw this on a powerpc64 power 9 machine.
commit 7232f7c4c2d727431096a7ecfcf4ad4db71dcf2a (HEAD)
Author: Jason Merrill <jason@redhat.com>
Date: Sun Jun 13 14:00:12 2021 -0400
Executing on host: /home3/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home3/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled146254.cc
-fdiagnostics-plain-output -S -o exceptions_enabled146254.s (timeout = 300)
spawn -ignore SIGHUP /home3/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home3/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled146254.cc
-fdiagnostics-plain-output -S -o exceptions_enabled146254.s
FAIL: gcc.target/powerpc/stack-limit.c (test for excess errors)
Excess errors:
during RTL pass: pro_and_epilogue
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/stack-limit.c:10:1:
internal compiler error: in df_ref_record, at df-scan.c:2598
0x1059b0df df_ref_record
/home/seurer/gcc/git/gcc-test/gcc/df-scan.c:2598
0x1059bee7 df_uses_record
/home/seurer/gcc/git/gcc-test/gcc/df-scan.c:2888
0x1059c84f df_insn_refs_collect
/home/seurer/gcc/git/gcc-test/gcc/df-scan.c:3212
0x1059f07f df_insn_rescan(rtx_insn*)
/home/seurer/gcc/git/gcc-test/gcc/df-scan.c:1087
0x106554e7 emit_insn_after_1
/home/seurer/gcc/git/gcc-test/gcc/emit-rtl.c:4595
0x106554e7 emit_pattern_after_noloc
/home/seurer/gcc/git/gcc-test/gcc/emit-rtl.c:4643
0x1050e14f commit_one_edge_insertion(edge_def*)
/home/seurer/gcc/git/gcc-test/gcc/cfgrtl.c:2051
0x10513d57 commit_edge_insertions()
/home/seurer/gcc/git/gcc-test/gcc/cfgrtl.c:2103
0x1073e6d7 thread_prologue_and_epilogue_insns()
/home/seurer/gcc/git/gcc-test/gcc/function.c:6147
0x1073edaf rest_of_handle_thread_prologue_and_epilogue
/home/seurer/gcc/git/gcc-test/gcc/function.c:6521
0x1073edaf execute
/home/seurer/gcc/git/gcc-test/gcc/function.c:6597
next reply other threads:[~2021-06-21 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 20:33 seurer at gcc dot gnu.org [this message]
2021-06-21 20:35 ` [Bug middle-end/101157] " pinskia at gcc dot gnu.org
2021-06-22 6:25 ` marxin at gcc dot gnu.org
2021-06-22 6:32 ` pinskia at gcc dot gnu.org
2021-06-22 6:54 ` rguenth at gcc dot gnu.org
2021-06-22 15:26 ` seurer at gcc dot gnu.org
2021-06-22 18:12 ` marxin at gcc dot gnu.org
2021-09-03 2:41 ` bergner at gcc dot gnu.org
2021-09-03 2:49 ` seurer at gcc dot gnu.org
2021-09-03 14:55 ` bergner at gcc dot gnu.org
2021-11-17 7:39 ` pinskia at gcc dot gnu.org
2021-11-17 7:40 ` 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-101157-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).