From: Stephen Crane <sjc@immunant.com>
To: Sriraman Tallam <tmsriram@google.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 22:16:00 -0000 [thread overview]
Message-ID: <CAB7K5r6qyBk2_UX+qXj-ZYWHLx29a1zL-cbKMNdZKW7GNhGZzA@mail.gmail.com> (raw)
In-Reply-To: <CAAs8Hmx=TAefxd22HctUaNP5wcASOv34_zRuzYsm1_7rLttJYw@mail.gmail.com>
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?
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 22:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 1:46 [PATCH 2/2] " Stephen Crane
2017-10-11 0:52 ` Stephen Crane
2017-10-11 7:09 ` Sriraman Tallam via binutils
2017-10-14 1:00 ` Stephen Crane
2017-10-14 5:47 ` Sriraman Tallam via binutils
2017-10-20 0:51 ` Cary Coutant
2017-10-20 21:49 ` [PATCH] " Stephen Crane
2017-11-08 0:39 ` Stephen Crane
2017-11-08 22:37 ` Cary Coutant
2017-11-10 1:24 ` Stephen Crane
2017-11-10 5:06 ` Cary Coutant
2017-11-10 16:29 ` Sriraman Tallam via binutils
2017-11-10 22:11 ` Sriraman Tallam via binutils
2017-12-11 22:10 ` Sriraman Tallam via binutils
2017-12-11 22:16 ` Stephen Crane [this message]
2017-12-11 22:33 ` Sriraman Tallam via binutils
2017-12-11 23:03 ` Sriraman Tallam via binutils
2017-12-12 18:51 ` Stephen Crane
-- strict thread matches above, loose matches on Subject: below --
2017-08-25 5:49 Stephen Crane
2017-09-14 22:16 ` Stephen Crane
2017-09-20 21:51 ` Cary Coutant
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=CAB7K5r6qyBk2_UX+qXj-ZYWHLx29a1zL-cbKMNdZKW7GNhGZzA@mail.gmail.com \
--to=sjc@immunant.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).