From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] Don't call lto-wrapper for ar and ranlib
Date: Mon, 24 Feb 2020 23:41:00 -0000 [thread overview]
Message-ID: <20200224234055.GF5570@bubble.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOoZVRWDpw1RefCYHG6N9tXv63TM5zRG+TgJMWWgJkn6SA@mail.gmail.com>
On Mon, Feb 24, 2020 at 04:58:40AM -0800, H.J. Lu wrote:
> On Fri, Feb 21, 2020 at 5:20 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > Since ar and ranlib don't need to know symbol types to work properly,
> > we should avoid calling lto-wrapper for them to speed them up.
>
> Nick, Alan, is this patch OK for master?
Looks OK to me for both master and 2.34.
> Nick, is this patch OK for backport to 2.34 branch?
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-02-24 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:20 H.J. Lu
2020-02-24 12:59 ` H.J. Lu
2020-02-24 23:41 ` Alan Modra [this message]
2020-02-25 14:46 ` Nick Clifton
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=20200224234055.GF5570@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).