From: "Sriraman Tallam via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Stephen Crane <sjc@immunant.com>
Cc: Cary Coutant <ccoutant@gmail.com>,
Binutils <binutils@sourceware.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files
Date: Mon, 11 Dec 2017 23:03:00 -0000 [thread overview]
Message-ID: <CAAs8HmxK9XU0GfgRofwrxFzUQ1jmFyPYiJM=_7WahYFZc5SdxQ@mail.gmail.com> (raw)
In-Reply-To: <CAB7K5r6qyBk2_UX+qXj-ZYWHLx29a1zL-cbKMNdZKW7GNhGZzA@mail.gmail.com>
On Mon, Dec 11, 2017 at 2:16 PM, Stephen Crane <sjc@immunant.com> wrote:
> Thanks for committing the GCC portion and following up on this. I had
> been meaning to write and ask. I don't have commit privs for binutils,
> so either you or Cary will have to commit the binutils patch as well,
> if it's not too much trouble. I think much has changed to need a
> rebase?
I just committed your patch. I had to make one very minor change to
plugin_new_section_layout.c to compile, move the loop initialization
declaration outside as that is not allowed on C. I tested the patch.
Thanks
Sri
>
> Thanks,
> Stephen
>
> On Mon, Dec 11, 2017 at 2:10 PM, Sriraman Tallam <tmsriram@google.com> wrote:
>> On Thu, Nov 9, 2017 at 9:04 PM, Cary Coutant <ccoutant@gmail.com> wrote:
>>>> include/ChangeLog:
>>>> 2017-11-09 Stephen Crane <sjc@immunant.com>
>>>>
>>>> * plugin-api.h: Add new plugin hook to allow processing of input
>>>> files added by a plugin.
>>>> (ld_plugin_new_input_handler): New funcion hook type.
>>>> (ld_plugin_register_new_input): New interface.
>>>> (LDPT_REGISTER_NEW_INPUT_HOOK): New enum val.
>>>> (tv_register_new_input): New member.
>>>>
>>>>
>>>> gold/ChangeLog:
>>>> 2017-11-09 Stephen Crane <sjc@immunant.com>
>>>>
>>>> * plugin.cc (Plugin::load): Include hooks for register_new_input
>>>> in transfer vector.
>>>> (Plugin::new_input): New function.
>>>> (register_new_input): New function.
>>>> (Plugin_manager::claim_file): Call Plugin::new_input if in
>>>> replacement phase.
>>>> * plugin.h (Plugin::set_new_input_handler): New function.
>>>> * testsuite/plugin_new_section_layout.c: New plugin to test
>>>> new_input plugin API.
>>>> * testsuite/plugin_final_layout.sh: Add new input test.
>>>> * testsuite/Makefile.am (plugin_layout_new_file): New test case.
>>>> * testsuite/Makefile.in: Regenerate.
>>>
>>> These are OK. Thanks!
>>>
>>> Sri, I'm out of town through 11/18, and won't be able to commit the
>>> include/ patch to GCC before Stage 1 ends. Can you take care of it?
>>> (If not, I'll take care of it when I get back -- it was approved
>>> during Stage 1, so I think it's OK to commit early in Stage 3,
>>> especially since it's nothing but new declarations.)
>>
>> Stephen, I was looking at binutils and realized this patch has not
>> been committed yet. I only committed the GCC portion, plugin-api.h.
>>
>> Thanks
>> Sri
>>
>>>
>>> -cary
next prev parent reply other threads:[~2017-12-11 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB7K5r44EtJiXZOiQzM+qqymKjooOTbyb7gikfOxbk7yoyrywg@mail.gmail.com>
[not found] ` <CAAs8HmyFiWr6SKG-p+_zHGVBw7sSAoudO5b0qe_zaVPLK1HGmw@mail.gmail.com>
[not found] ` <CAB7K5r4DaPN+bq=evZv5zmiEA3BQ8RCv-8ex6889J-AyNyCxdA@mail.gmail.com>
[not found] ` <CAAs8HmxEMuOn=cjKOn_gNRv0ve4yshvt2VwLJAasq7d4fVc0Kg@mail.gmail.com>
[not found] ` <CAJimCsGtFxP9uNivzrz_uV=V7FyznbzDAE8ZTKRR_+wPdJHO5A@mail.gmail.com>
[not found] ` <87376dlcb9.fsf_-_@immunant.com>
[not found] ` <CAB7K5r5DvEE7dU7PwhquXKx=gjteQzmcv=1BbG-tBzXGa23CUg@mail.gmail.com>
[not found] ` <CAJimCsE9tF6toFSeyv2M-qSVmX_cNQySCb62ENTy4uhvtDRWTA@mail.gmail.com>
2017-11-10 2:35 ` Stephen Crane
2017-11-10 7:24 ` Cary Coutant
2017-11-10 16:55 ` Sriraman Tallam via gcc-patches
2017-11-10 22:30 ` Sriraman Tallam via gcc-patches
2017-12-11 22:10 ` Sriraman Tallam via gcc-patches
2017-12-11 22:16 ` Stephen Crane
2017-12-11 22:33 ` Sriraman Tallam via gcc-patches
2017-12-11 23:03 ` Sriraman Tallam via gcc-patches [this message]
2017-12-12 18:51 ` Stephen Crane
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='CAAs8HmxK9XU0GfgRofwrxFzUQ1jmFyPYiJM=_7WahYFZc5SdxQ@mail.gmail.com' \
--to=gcc-patches@gcc.gnu.org \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=sjc@immunant.com \
--cc=tmsriram@google.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).