From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Alan Modra <amodra@gmail.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PING] LD: Hidden/internal versioned symbol preemption bug
Date: Wed, 29 Aug 2012 00:09:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1208282129190.12630@tp.orcam.me.uk> (raw)
In-Reply-To: <20120819090719.GA3947@bubble.grove.modra.org>
On Sun, 19 Aug 2012, Alan Modra wrote:
> > * elflink.c (_bfd_elf_merge_symbol): Also override the version
> > a dynamic symbol defaulted to if preempted with a hidden or
> > internal definition.
>
> This is OK. What we had before was a bit of a mess. The followup
> testsuite and ppc patches are OK too.
Thanks for your review, I have applied all the three patches now.
Maciej
prev parent reply other threads:[~2012-08-28 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 0:14 Maciej W. Rozycki
2012-08-18 0:27 ` H.J. Lu
2012-08-19 13:48 ` Alan Modra
2012-08-29 0:09 ` Maciej W. Rozycki [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=alpine.DEB.1.10.1208282129190.12630@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.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).