public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Cary Coutant <ccoutant@gmail.com>
To: Stephen Crane <sjc@immunant.com>
Cc: Binutils <binutils@sourceware.org>,
	Sriraman Tallam <tmsriram@google.com>
Subject: Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files
Date: Wed, 20 Sep 2017 21:51:00 -0000	[thread overview]
Message-ID: <CAJimCsFahXRjd2a2KJpC69naBs7xKtU7YjS+c9BR9uNCCbZMSg@mail.gmail.com> (raw)
In-Reply-To: <CAB7K5r7b=W2jBF8KEjBwTzJ-BY=seE0jNMm4LHGEPP8qc3zR+g@mail.gmail.com>

> I just wanted to ping this patch and see if this change (or something
> else that allows unique segments in plugin-created objects) can be
> added to the plugin API.
>
> On Thu, Aug 24, 2017 at 10:48 PM, Stephen Crane <sjc@immunant.com> wrote:
>> I have a gold plugin that needs to call the
>> unique_segment_for_sections interface for sections in an input file
>> created by a plugin. Specifically, I want to assign a section created
>> during LTO to a unique output segment with special flags. Here is a
>> patch that allows this use case by adding a callback that gives the
>> plugin the opportunity to get an input handle for plugin-created input
>> files. Could this be added to the gold plugin API? Is there a better
>> way to do this?

This seems reasonable, although I haven't given your patch a good look
yet. Before we put this in gold, though, you should post your proposed
change to the plugin interface (i.e., plugin-api.h) to the gcc-patches
mailing list for review there (please cc me), then be prepared to
update the whopr/driver wiki page on the GCC wiki:

https://gcc.gnu.org/wiki/whopr/driver

The patch to plugin-api.h will need to be applied first on the GCC
tree, then synced back to the binutils tree.

I'd suggest you also cc Sriraman Tallam (cc'ed here). The API
extensions for assigning sections to unique segments are his, so he
may have some useful feedback for you.

-cary

  reply	other threads:[~2017-09-20 21:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  5:49 Stephen Crane
2017-09-14 22:16 ` Stephen Crane
2017-09-20 21:51   ` Cary Coutant [this message]
2017-09-26  1:46 [PATCH 2/2] " 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
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

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=CAJimCsFahXRjd2a2KJpC69naBs7xKtU7YjS+c9BR9uNCCbZMSg@mail.gmail.com \
    --to=ccoutant@gmail.com \
    --cc=binutils@sourceware.org \
    --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).