From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Commit: Update libiberty sources
Date: Mon, 5 Jul 2021 16:25:07 +0100 [thread overview]
Message-ID: <7c3926c7-9200-d162-8dab-96626181e0d3@redhat.com> (raw)
In-Reply-To: <CAMe9rOoNY0iCJDcUUP2iUyU94J-NdpX6PFZU-vm15h65-Y04mg@mail.gmail.com>
Hi H.J.
> My patch is needed to build binutils with LTO. I submitted a patch for GCC:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574405.html
Very well. I have reappplied your patch to the mainline and 2.37 branch sources.
Cheers
Nick
next prev parent reply other threads:[~2021-07-05 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 12:56 Nick Clifton
2021-07-04 12:56 ` Alan Modra
2021-07-04 13:54 ` H.J. Lu
2021-07-05 15:25 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-26 14:46 Nick Clifton
2018-01-10 13:59 Nick Clifton
2018-01-15 16:03 ` Szabolcs Nagy
2018-01-15 16:08 ` H.J. Lu
2017-09-01 9:59 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=7c3926c7-9200-d162-8dab-96626181e0d3@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.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).