From: Alexander Zaitsev <zamazan4ik@tut.by>
To: gcc@gcc.gnu.org
Subject: Document how to build PGO-optimized GCC version
Date: Wed, 28 Dec 2022 06:36:57 +0100 [thread overview]
Message-ID: <387a052a-60f2-3d03-38d4-dcff21aaaa03@tut.by> (raw)
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hello.
We are using GCC for our C++ projects. Our projects are huge, commit
rate is quite huge, so our CI workers are always busy (so as any other
CI workers, honestly). Since we want to increase build speed, one of the
option is to optimize the compiler itself. Sounds like a good case for PGO.
Clang has the infrastructure for building the Clang itself with PGO:
https://llvm.org/docs/HowToBuildWithPGO.html . I have tried to find
something like that for GCC but with no success.
My proposal is:
* add support for building PGO-optimized GCC into the GCC build
infrastructure
* add documentation to the GCC site, how to build GCC with PGO
optimizations
* (if GCC community provides prebuilt gcc binaries) use PGO for the
prebuilt binaries. E.g. Clang and rustc already uses this approach.
Any feedback is appreciated.
Thanks in advance!
--
Best regards,
Alexander Zaitsev
next reply other threads:[~2022-12-28 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 5:36 Alexander Zaitsev [this message]
2022-12-28 5:48 ` Andrew Pinski
2022-12-28 8:57 ` Martin Liška
2022-12-28 7:22 ` NightStrike
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=387a052a-60f2-3d03-38d4-dcff21aaaa03@tut.by \
--to=zamazan4ik@tut.by \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).