Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Matthias Klose <doko@ubuntu.com>,
	gcc-patches@gcc.gnu.org, binutils@sourceware.org,
	gdb-patches@sourceware.org
Subject: Re: V3 [PATCH 0/5] Support the PGO build for binutils+gdb
Date: Sat, 2 Jan 2021 13:22:22 -0600	[thread overview]
Message-ID: <20210102192222.GA30983@gate.crashing.org> (raw)
In-Reply-To: <20201219181036.178248-1-hjl.tools@gmail.com>

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

  parent reply	other threads:[~2021-01-02 19:25 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 ` Segher Boessenkool [this message]
2021-01-02 19:46   ` V3 [PATCH 0/5] Support the PGO build for binutils+gdb H.J. Lu via Gdb-patches

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=20210102192222.GA30983@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=binutils@sourceware.org \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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