public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] plugin: Don't invoke LTO-wrapper
Date: Fri, 20 Mar 2020 08:59:03 +0100	[thread overview]
Message-ID: <32d05f6a-8e88-e42b-7d7e-561931c9467f@suse.cz> (raw)
In-Reply-To: <CAMe9rOpbeZ3Pcg9TwOg+vt6NbgOPk=tBspe1BLSA7vLG9nZqOg@mail.gmail.com>

On 3/20/20 5:42 AM, H.J. Lu via Binutils wrote:
> On Thu, Mar 19, 2020 at 7:38 PM Alan Modra <amodra@gmail.com> wrote:
>>
>> On Thu, Mar 19, 2020 at 09:50:17AM -0700, H.J. Lu via Binutils wrote:
>>> Since LTO plugin may generate more than one ltrans.o file from one input
>>> IR object as LTO wrapper ignores -flto-partition=none:
>>>
>>> lto-wrapper.c:608:
>>>
>>>     604          /* Drop arguments that we want to take from the link line.  */
>>>     605          case OPT_flto_:
>>>     606          case OPT_flto:
>>>     607          case OPT_flto_partition_:
>>>     608            continue;
>>>
>>> the LTO wrapper approach is not only slow but also unreliable.  Since
>>> the LTO plugin API has been extended to add LDPT_ADD_SYMBOLS_V2 with
>>> symbol type and section kind, we can use LDPT_ADD_SYMBOLS_V2 to get
>>> symbol type, instead of invoking the LTO wrapper.
>>>
>>>        PR binutils/25640
>>>        * plugin.c (plugin_list_entry): Add has_symbol_type.
>>>        (add_symbols_v2): New function.
>>>        (bfd_plugin_open_input): Don't invoke LTO wrapper if LTO plugin
>>>        provides symbol type.
>>>        (try_load_plugin): Add LDPT_ADD_SYMBOLS_V2.
>>>        (bfd_plugin_canonicalize_symtab): Use LTO plugin symbol type if
>>>        available.
>>
>> OK.  Are you going to remove the LTO wrapper code from binutils?
> 
> Here is the patch to remove the LTO wrapper code.
> 
> OK for master?
> 
> Thanks.
> 

Hello.

Thank you very much for the patches. Can you please than backport this
to 2.34 branch?

Thanks,
Martin

  reply	other threads:[~2020-03-20  7:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 16:50 [PATCH] plugin: Use LDPT_ADD_SYMBOLS_V2 to get symbol type H.J. Lu
2020-03-20  2:38 ` Alan Modra
2020-03-20  4:42   ` [PATCH] plugin: Don't invoke LTO-wrapper H.J. Lu
2020-03-20  7:59     ` Martin Liška [this message]
2020-03-20 11:13       ` H.J. Lu
2020-03-20 14:08         ` Martin Liška
2020-03-20 14:23           ` H.J. Lu
2020-03-23 15:04             ` Martin Liška
2020-03-24 10:47               ` Martin Liška
2020-03-24 11:34                 ` [PATCH] include: Sync plugin-api.h with GCC H.J. Lu
2020-03-25 13:36                   ` Martin Liška
2020-03-25 13:38                     ` Martin Liška
2020-03-25 13:41                     ` Nick Clifton
2020-03-25 13:42                       ` H.J. Lu
2020-03-25 14:10                         ` H.J. Lu
2020-03-20 10:19     ` [PATCH] plugin: Don't invoke LTO-wrapper Alan Modra
2020-03-20 10:52       ` H.J. Lu

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=32d05f6a-8e88-e42b-7d7e-561931c9467f@suse.cz \
    --to=mliska@suse.cz \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).