public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91518] [9 Regression] segfault when run CPU2006 465.tonto since r263875
Date: Mon, 11 May 2020 01:44:20 +0000 [thread overview]
Message-ID: <bug-91518-4-CF9U53zB9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91518-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91518
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Xiong Hu Luo
<luoxhu@gcc.gnu.org>:
https://gcc.gnu.org/g:b8da02efe62611a9f173c699a76010de5b916d33
commit r9-8583-gb8da02efe62611a9f173c699a76010de5b916d33
Author: Xionghu Luo <luoxhu@linux.ibm.com>
Date: Sun May 10 20:27:38 2020 -0500
rs6000: Don't use HARD_FRAME_POINTER_REGNUM if it's not live in
pro_and_epilogue (PR91518)
Backport from master.
This bug is exposed by FRE refactor of r263875. Comparing the fre
dump file shows no obvious change of the segment fault function proves
it to be a target issue.
frame_pointer_needed is set to true in reload pass setup_can_eliminate,
but regs_ever_live[31] is false, pro_and_epilogue uses it without live
check causing CPU2006 465.tonto segment fault of loading from invalid
addresses due to r31 not saved/restored. Thus, add
HARD_FRAME_POINTER_REGNUM
live check with frame_pointer_needed_indeed when generating
pro_and_epilogue
instructions.
gcc/ChangeLog
2020-05-11 Xiong Hu Luo <luoxhu@linux.ibm.com>
Backport from master.
2020-04-27 Xiong Hu Luo <luoxhu@linux.ibm.com>
PR target/91518
* config/rs6000/rs6000.c (frame_pointer_needed_indeed):
New variable.
(rs6000_emit_prologue_components):
Check with frame_pointer_needed_indeed.
(rs6000_emit_epilogue_components): Likewise.
(rs6000_emit_prologue): Likewise.
(rs6000_emit_epilogue): Set frame_pointer_needed_indeed.
next prev parent reply other threads:[~2020-05-11 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91518-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug target/91518] [9/10 " jakub at gcc dot gnu.org
2020-03-25 21:05 ` law at redhat dot com
2020-03-26 7:07 ` rguenth at gcc dot gnu.org
2020-03-26 7:17 ` luoxhu at gcc dot gnu.org
2020-04-01 8:43 ` rguenth at gcc dot gnu.org
2020-04-27 1:48 ` cvs-commit at gcc dot gnu.org
2020-04-27 6:25 ` [Bug target/91518] [9 " rguenth at gcc dot gnu.org
2020-05-11 1:44 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-12 0:42 ` luoxhu 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-91518-4-CF9U53zB9E@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).