From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "Martin Liška" <mliska@suse.cz>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: 2.36 Branch imminent
Date: Tue, 15 Dec 2020 05:57:26 -0800 [thread overview]
Message-ID: <CAMe9rOp7hS8u5n7eCj1T8t+F5mpqS4ZFaSMb8-Yp+Depx1oEpA@mail.gmail.com> (raw)
In-Reply-To: <c8368675-9c14-e975-e460-e17fb2bbcf08@redhat.com>
On Tue, Dec 15, 2020 at 5:51 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi H.J.
>
> > I'd like to enable PGO/LTO build for binutils:
> >
> > https://sourceware.org/pipermail/binutils/2020-October/113943.html
> >
> > It can speed up the assembler significantly.
>
> I'm all for this. The binutils parts are approved although I assume
> that you will still need buy in from the gdb and gcc folks.
Toplevel files are shared with GCC. But my changes are disabled for GCC.
I got no feedbacks from GCC nor GDB developers. What should I do next?
--
H.J.
next prev parent reply other threads:[~2020-12-15 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 11:44 Nick Clifton
2020-12-14 11:48 ` H.J. Lu
2020-12-14 12:45 ` Nick Clifton
2020-12-15 13:32 ` H.J. Lu
2020-12-15 13:51 ` Nick Clifton
2020-12-15 13:57 ` H.J. Lu [this message]
2020-12-15 17:00 ` Nick Clifton
2020-12-15 17:15 ` Tom Tromey
2020-12-15 17:25 ` H.J. Lu
2020-12-15 17:33 ` Tom Tromey
2020-12-15 18:25 ` H.J. Lu
2021-01-05 10:50 ` Nick Clifton
2021-01-05 22:55 ` H.J. Lu
2021-01-07 12:10 ` Nick Clifton
2021-01-09 14:37 ` Support the PGO build for binutils+gdb (2.36 Branch imminent) H.J. Lu
2021-01-13 12:47 ` 2.36 Branch imminent Pedro Alves
2021-01-06 7:51 ` Kyrylo Tkachov
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=CAMe9rOp7hS8u5n7eCj1T8t+F5mpqS4ZFaSMb8-Yp+Depx1oEpA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=mliska@suse.cz \
--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).