From: "H.J. Lu" <hjl.tools@gmail.com>
To: binutils@sourceware.org
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
Matthias Klose <doko@ubuntu.com>, Martin Liska <mliska@suse.cz>
Subject: V3 [PATCH 0/5] Support the PGO build for binutils+gdb
Date: Sat, 19 Dec 2020 10:10:31 -0800 [thread overview]
Message-ID: <20201219181036.178248-1-hjl.tools@gmail.com> (raw)
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.
Tested PGO/LTO builds for GDB and binutils with GCC 11 on Fedora 33.
Changes from V2:
1. Pass PGO_BUILD_TRAINING=yes for PGO build training.
2. Set TESTS to gdb.dwarf2/*.exp for GDB PGO build training.
3. gnulib: Support variables from the top level Makefile.
Changes from V1:
1. Pass -ffat-lto-objects together with -flto=jobserver.
2. Pass -i to make to ignore "make check" errors in PGO training runs.
H.J. Lu (5):
GCC: Pass --plugin to AR and RANLIB
Binutils: Pass --plugin to AR and RANLIB
Support the PGO build for binutils+gdb
Set TESTS to gdb.dwarf2/*.exp for PGO build training
gnulib: Support variables from the top level Makefile
Makefile.in | 68 ++++++++++++-
Makefile.tpl | 63 +++++++++++-
bfd/configure | 27 ++++-
binutils/configure | 27 ++++-
config/gcc-plugin.m4 | 28 ++++++
configure | 139 ++++++++++++++++++++++++-
configure.ac | 80 +++++++++++++++
gas/configure | 27 ++++-
gdb/testsuite/Makefile.in | 5 +
gnulib/Makefile.am | 39 ++++++++
gnulib/Makefile.in | 40 ++++++++
gprof/configure | 27 ++++-
ld/configure | 27 ++++-
libctf/configure | 27 ++++-
libiberty/Makefile.in | 5 +-
libiberty/aclocal.m4 | 1 +
libiberty/configure | 37 +++++++
libiberty/configure.ac | 12 +++
libtool.m4 | 25 ++++-
opcodes/configure | 27 ++++-
zlib/configure | 206 +++++++++++++++++++++++++++++++++++++-
21 files changed, 907 insertions(+), 30 deletions(-)
--
2.29.2
next reply other threads:[~2020-12-19 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 18:10 H.J. Lu [this message]
2020-12-19 18:10 ` V3 [PATCH 1/5] GCC: Pass --plugin to AR and RANLIB H.J. Lu
2020-12-19 18:10 ` V3 [PATCH 2/5] Binutils: " H.J. Lu
2020-12-19 18:10 ` V3 [PATCH 3/5] Support the PGO build for binutils+gdb H.J. Lu
2021-02-28 7:01 ` Mike Frysinger
2021-02-28 12:44 ` [PATCH] Add missing changes to Makefile.tpl H.J. Lu
2020-12-19 18:10 ` V3 [PATCH 4/5] Set TESTS to gdb.dwarf2/*.exp for PGO build training H.J. Lu
2020-12-19 18:10 ` V3 [PATCH 5/5] gnulib: Support variables from the top level Makefile H.J. Lu
2020-12-31 23:50 ` Joseph Myers
2021-01-01 0:06 ` H.J. Lu
2021-01-05 13:26 ` Christian Biesinger
2021-01-05 14:06 ` H.J. Lu
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
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=20201219181036.178248-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mliska@suse.cz \
/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).