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/96072] New: ICE: Segmentation fault (in add_reg_note)
Date: Mon, 06 Jul 2020 04:47:11 +0000 [thread overview]
Message-ID: <bug-96072-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96072
Bug ID: 96072
Summary: ICE: Segmentation fault (in add_reg_note)
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: 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: powerpc-*-linux-gnu
gcc-11.0.0 snapshot (g:cc9a9229285a26ac12bc8de53237ce9c4d42f867) ICEs when
compiling gcc/testsuite/gcc.target/pru/clobber-sp.c w/ -O1:
% powerpc-e300c3-linux-gnu-gcc-11.0.0 -O1 -w -c
gcc/testsuite/gcc.target/pru/clobber-sp.c
during RTL pass: pro_and_epilogue
gcc/testsuite/gcc.target/pru/clobber-sp.c: In function 'test1':
gcc/testsuite/gcc.target/pru/clobber-sp.c:24:1: internal compiler error:
Segmentation fault
24 | }
| ^
0xe74ba6 crash_signal
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/toplev.c:328
0xe09f99 add_reg_note(rtx_def*, reg_note, rtx_def*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/rtlanal.c:2404
0x1271d6a rs6000_emit_epilogue(epilogue_type)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/config/rs6000/rs6000-logue.c:4884
0x15803ce gen_epilogue()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/config/rs6000/rs6000.md:13210
0x11f5bf8 target_gen_epilogue
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/config/rs6000/rs6000.md:10475
0xb2d46f make_epilogue_seq
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/function.c:5822
0xb2d55f thread_prologue_and_epilogue_insns()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/function.c:5904
0xb2dc86 rest_of_handle_thread_prologue_and_epilogue
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/function.c:6394
0xb2dc86 execute
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200705/work/gcc-11-20200705/gcc/function.c:6470
next reply other threads:[~2020-07-06 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 4:47 asolokha at gmx dot com [this message]
2020-08-11 4:13 ` [Bug target/96072] " asolokha at gmx dot com
2020-08-19 7:30 ` asolokha at gmx dot com
2022-09-13 22:25 ` segher at gcc dot gnu.org
2022-09-14 2:33 ` asolokha at gmx dot com
2022-09-14 12:20 ` linkw at gcc dot gnu.org
2022-09-14 12:23 ` linkw at gcc dot gnu.org
2022-09-15 5:44 ` [Bug target/96072] [10/11/12 Regression] " linkw at gcc dot gnu.org
2022-09-26 5:34 ` cvs-commit at gcc dot gnu.org
2022-10-19 9:05 ` cvs-commit at gcc dot gnu.org
2022-10-19 11:24 ` cvs-commit at gcc dot gnu.org
2022-10-20 2:16 ` cvs-commit at gcc dot gnu.org
2022-10-20 2:28 ` linkw 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-96072-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).