From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] lto: Don't add indirect symbols for versioned aliases in IR
Date: Tue, 11 Apr 2023 10:07:18 +0100 [thread overview]
Message-ID: <d262e982-28af-e51b-8d59-c83f0d910337@redhat.com> (raw)
In-Reply-To: <CAMe9rOqKOMA2aVonnB_TMX_5OKCmeWcZshMatnPZtfuYykBpbA@mail.gmail.com>
Hi H.J.
>> On Thu, Mar 30, 2023 at 09:42:14AM -0700, H.J. Lu via Binutils wrote:
>>> bfd/
>>>
>>> PR ld/30281
>>> * elflink.c (elf_link_add_object_symbols): Don't add indirect
>>> symbols for ".symver foo, foo@FOO" aliases in IR.
>>>
>>> ld/
>>>
>>> PR ld/30281
>>> * testsuite/ld-plugin/lto.exp: Add PR ld/30281 test.
>>> * testsuite/ld-plugin/pr30281.t: New file.
>>> * testsuite/ld-plugin/pr30281.c: Likewise.
> Is this OK for 2.40 branch?
Sure - please go ahead.
Cheers
Nick
prev parent reply other threads:[~2023-04-11 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 16:42 H.J. Lu
2023-03-30 21:27 ` Alan Modra
2023-04-03 18:24 ` H.J. Lu
2023-04-11 9:07 ` Nick Clifton [this message]
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=d262e982-28af-e51b-8d59-c83f0d910337@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).