From: Alan Modra <amodra@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [POWER10] __morestack calls from pcrel code
Date: Thu, 22 Jul 2021 14:25:44 +0930 [thread overview]
Message-ID: <YPj6UN8vgDotz0MV@squeak.grove.modra.org> (raw)
In-Reply-To: <CAGWvny=ZuYZAKzMejDygoxDcr=h8uyk-oZm_wg5xaTEP8jGRsw@mail.gmail.com>
On Wed, Jul 21, 2021 at 08:59:04AM -0400, David Edelsohn wrote:
> On Wed, Jul 21, 2021 at 4:29 AM Alan Modra <amodra@gmail.com> wrote:
> >
> > On Wed, Jul 14, 2021 at 08:24:16PM -0400, David Edelsohn wrote:
> > > > > > * config/rs6000/morestack.S (R2_SAVE): Define.
> > > > > > (__morestack): Save and restore r2. Set up r2 for called
> > > > > > functions.
> > >
> > > This patch is okay.
> >
> > Thanks David, the patch is needed on gcc-11 and gcc-10 too.
> > OK for the branches too?
>
> Backports are fine, but I believe that Richi is planning to cut GCC 11
> RC today, so you really should check with him about a backport at the
> last minute.
Hi Richard,
Is this patch OK at this late stage for the gcc-11 branch?
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573978.html
The impacts of the bug are segfaults and other undesirable behaviour
with Go (or more generally -fsplit-stack) on power10 when libgcc is
not power10 pcrel. A non-pcrel libgcc is very likely how distros
will ship gcc.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2021-07-22 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 6:55 Alan Modra
2021-06-30 20:06 ` Tulio Magno Quites Machado Filho
2021-07-15 0:01 ` Alan Modra
2021-07-15 0:24 ` David Edelsohn
[not found] ` <YPfa4cOkPbk/mzMF@squeak.grove.modra.org>
[not found] ` <CAGWvny=ZuYZAKzMejDygoxDcr=h8uyk-oZm_wg5xaTEP8jGRsw@mail.gmail.com>
2021-07-22 4:55 ` Alan Modra [this message]
2021-07-22 6:41 ` Richard Biener
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=YPj6UN8vgDotz0MV@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.com \
/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).