From: "H.J. Lu" <hjl.tools@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: PR28827 testcase
Date: Sat, 5 Feb 2022 20:26:55 -0800 [thread overview]
Message-ID: <Yf9ODzTSwBn21kKH@gmail.com> (raw)
In-Reply-To: <Yf9Lz8CtPsRe9JX5@squeak.grove.modra.org>
On Sun, Feb 06, 2022 at 02:47:19PM +1030, Alan Modra via Binutils wrote:
> On Sat, Feb 05, 2022 at 10:39:50AM +0000, Nick Clifton wrote:
> > Hi Alan, Hi Fangrui,
> >
> > > This testcase triggers a stub sizing error with the patches applied
> > > for PR28743 (commit 2f83249c13d8 and c804c6f98d34).
> > >
> > > PR 28827
> > > * testsuite/ld-powerpc/pr28827-1.s,
> > > * testsuite/ld-powerpc/pr28827-1.d: New test.
> > > * testsuite/ld-powerpc/powerpc.exp: Run it.
> >
> > Given the importance of the PowerPC target, I am going to hold
> > off from creating the 2.38 release until this issue is fixed.
>
> Thanks, I appreciate it.
>
> > I do hope however that it can be resolved soon....
>
> The solution is to revert HJ's two relro patches on the branch. That
> will let you immediately make a release. Despite being raised by
> Florian, I don't believe PR28743 is an important bug to fix just
> before a release. Our relro support has sometimes created a hole for
> *years*.
>
> Of course, the patches ought to be reverted on mainline too,
> separately from whatever solution we finally adopt for PR28743.
>
Why make removing the 1-page gap before the PT_GNU_RELRO segment opt-in?
https://sourceware.org/pipermail/binutils/2022-February/119625.html
H.J.
next prev parent reply other threads:[~2022-02-06 4:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 6:55 Alan Modra
2022-02-05 7:43 ` Fangrui Song
2022-02-05 10:00 ` Alan Modra
2022-02-05 10:39 ` Nick Clifton
2022-02-06 4:17 ` Alan Modra
2022-02-06 4:26 ` H.J. Lu [this message]
2022-02-06 22:54 ` Alan Modra
2022-02-06 23:38 ` H.J. Lu
2022-02-07 3:15 ` Alan Modra
2022-02-07 4:05 ` H.J. Lu
2022-02-07 5:32 ` Alan Modra
2022-02-08 11:41 ` Nick Clifton
2022-02-08 13:03 ` H.J. Lu
2022-02-08 23:48 ` Alan Modra
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=Yf9ODzTSwBn21kKH@gmail.com \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).