From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Alan Modra <amodra@gmail.com>, GDB <gdb-patches@sourceware.org>,
Nick Clifton <nickc@redhat.com>
Subject: Re: Fwd: GDB 7.8 update (getting closer, new pre-release)
Date: Mon, 28 Jul 2014 19:04:00 -0000 [thread overview]
Message-ID: <CAMe9rOrqW=EzkbFs+JQWoNLOz4GN9ej1CBHPvgB+E-=YCZ1XEQ@mail.gmail.com> (raw)
In-Reply-To: <20140728151448.GA6644@adacore.com>
On Mon, Jul 28, 2014 at 8:14 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=144bed8d4d8a1bdc0067f55f2ee71c07e5594677
>> > > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=cca5b8b64b3286bb96cd7a2c18232d1acea85cd9
>> > >
>> > > in GDB 7.8. It properly disassembles PLT section in libc.so with
>> > > IFUNC.
>> >
>> > Can you please have one of the binutils maintainers assess the risk
>> > level of backporting these patches into 7.8?
>>
>> I've become a little rusty on the x86 target code but it looks OK to
>> me. The simple approach that HJ has taken is quite suited to a
>> release branch, as compared to redesigning x86_64 ifunc support..
>> (The latter might be preferable on mainline to avoid the reloc
>> scanning, if possible, but I leave that decision to HJ.)
>
> Thanks, Alan.
>
> HJ,
>
> if this hasn't been ported to the branch yet, please go ahead now.
>
I checked them into 7.8 branch.
Thanks.
--
H.J.
next prev parent reply other threads:[~2014-07-28 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 13:39 Joel Brobecker
2014-07-17 15:07 ` H.J. Lu
2014-07-17 22:19 ` Joel Brobecker
[not found] ` <CAMe9rOp05O-S-Pg1cEiFm+FdzknDSwJg3FTrob-K=UPXKSMmEA@mail.gmail.com>
2014-07-20 0:56 ` Fwd: " Alan Modra
2014-07-28 18:18 ` Joel Brobecker
2014-07-28 19:04 ` H.J. Lu [this message]
2014-07-17 18:23 ` Doug Evans
2014-07-18 19:27 ` Doug Evans
2014-07-28 20:20 ` Edjunior Barbosa Machado
2014-07-28 20:23 ` Joel Brobecker
2014-07-28 21:47 ` Edjunior Barbosa Machado
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='CAMe9rOrqW=EzkbFs+JQWoNLOz4GN9ej1CBHPvgB+E-=YCZ1XEQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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