From: "H.J. Lu via Gdb-patches" <gdb-patches@sourceware.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Matthias Klose <doko@ubuntu.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GDB <gdb-patches@sourceware.org>
Subject: Re: V3 [PATCH 0/5] Support the PGO build for binutils+gdb
Date: Sat, 2 Jan 2021 11:46:00 -0800 [thread overview]
Message-ID: <CAMe9rOqB+gEmZ8-ybXabOFFJSDmFSFv1kuduL8=jVbDLNJtkdw@mail.gmail.com> (raw)
In-Reply-To: <20210102192222.GA30983@gate.crashing.org>
On Sat, Jan 2, 2021 at 11:24 AM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> On Sat, Dec 19, 2020 at 10:10:31AM -0800, H.J. Lu via Gcc-patches wrote:
> > Add the --enable-pgo-build[=lto] configure option. When binutils+gdb
> > is not built together with GCC, --enable-pgo-build enables the PGO build:
> >
> > 1. First build with -fprofile-generate.
> > 2. Use "make maybe-check-*" to generate profiling data and pass -i to make
> > to ignore errors when generating profiling data.
> > 3. Use "make clean" to remove the previous build.
> > 4. Rebuild with -fprofile-use.
>
> Can this not use --with-build-config=? As the user interface I mean,
> you probably still need most of this code, but at least it will be more
> obvious how to handle conflicts in user-specified options.
>
>
> Segher
--with-build-config= is more or less for bootstrapping GCC. In case
of binutils, we don't build GCC. We only train GCC with binutils/GDB
testsuites.
--
H.J.
prev parent reply other threads:[~2021-01-02 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 18:10 H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 1/5] GCC: Pass --plugin to AR and RANLIB H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 2/5] Binutils: " H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 3/5] Support the PGO build for binutils+gdb H.J. Lu via Gdb-patches
2021-02-28 7:01 ` Mike Frysinger via Gdb-patches
2021-02-28 12:44 ` [PATCH] Add missing changes to Makefile.tpl H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 4/5] Set TESTS to gdb.dwarf2/*.exp for PGO build training H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 5/5] gnulib: Support variables from the top level Makefile H.J. Lu via Gdb-patches
2020-12-31 23:50 ` Joseph Myers
2021-01-01 0:06 ` H.J. Lu via Gdb-patches
2021-01-05 13:26 ` Christian Biesinger via Gdb-patches
2021-01-05 14:06 ` H.J. Lu via Gdb-patches
2021-01-02 19:22 ` V3 [PATCH 0/5] Support the PGO build for binutils+gdb Segher Boessenkool
2021-01-02 19:46 ` H.J. Lu via Gdb-patches [this message]
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='CAMe9rOqB+gEmZ8-ybXabOFFJSDmFSFv1kuduL8=jVbDLNJtkdw@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=segher@kernel.crashing.org \
/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