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/102107] protocol register (r12) corrupted before a tail call
Date: Tue, 21 Sep 2021 23:47:55 +0000 [thread overview]
Message-ID: <bug-102107-4-ATPcU9eSil@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102107-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102107
--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Segher Boessenkool
<segher@gcc.gnu.org>:
https://gcc.gnu.org/g:14b7e8ace8236bd341a182dc3ef044fe98de5525
commit r10-10144-g14b7e8ace8236bd341a182dc3ef044fe98de5525
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Wed Sep 8 13:10:30 2021 +0000
rs6000: Fix ELFv2 r12 use in epilogue
We cannot use r12 here, it is already in use as the GEP (for sibling
calls).
2021-09-08 Segher Boessenkool <segher@kernel.crashing.org>
PR target/102107
* config/rs6000/rs6000-logue.c (rs6000_emit_epilogue): For ELFv2
use
r11 instead of r12 for restoring CR.
(cherry picked from commit 86e6268cff328e27ee6f90e2afc35b6f437a25cd)
next prev parent reply other threads:[~2021-09-21 23:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 20:54 [Bug target/102107] New: " pc at us dot ibm.com
2021-08-27 21:01 ` [Bug target/102107] " pc at us dot ibm.com
2021-08-27 21:03 ` pc at us dot ibm.com
2021-08-28 21:56 ` pc at us dot ibm.com
2021-08-28 22:33 ` pc at us dot ibm.com
2021-08-30 16:24 ` pc at us dot ibm.com
2021-08-30 19:58 ` segher at gcc dot gnu.org
2021-08-30 20:19 ` wschmidt at gcc dot gnu.org
2021-08-30 20:42 ` pc at us dot ibm.com
2021-08-30 22:49 ` segher at gcc dot gnu.org
2021-08-30 23:42 ` segher at gcc dot gnu.org
2021-08-31 13:20 ` pc at us dot ibm.com
2021-08-31 15:22 ` segher at gcc dot gnu.org
2021-08-31 17:43 ` segher at gcc dot gnu.org
2021-09-01 17:50 ` segher at gcc dot gnu.org
2021-09-03 21:05 ` cvs-commit at gcc dot gnu.org
2021-09-03 21:08 ` segher at gcc dot gnu.org
2021-09-08 13:30 ` cvs-commit at gcc dot gnu.org
2021-09-21 23:45 ` cvs-commit at gcc dot gnu.org
2021-09-21 23:45 ` cvs-commit at gcc dot gnu.org
2021-09-21 23:47 ` cvs-commit at gcc dot gnu.org
2021-09-21 23:47 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-21 23:53 ` segher at gcc dot gnu.org
2021-09-27 22:26 ` pc at us dot ibm.com
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-102107-4-ATPcU9eSil@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).