public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
Date: Tue, 14 May 2024 08:50:20 +0000 [thread overview]
Message-ID: <bug-114412-4-0PMvr8r2kk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114412-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412
--- Comment #4 from Filip Kastl <pheeck at gcc dot gnu.org> ---
(In reply to Tamar Christina from comment #3)
> Hi Filip,
>
> Do you generate these runs with counters based PGO or compiler
> instrumentation?
>
> Just so I know before I start trying to reproduce them.
Hi Tamar,
By counters you mean some sort of hardware counters? I didn't know there were
multiple ways to do PGO with GCC.
I think that the answer to your question is "compiler instrumentation". I just
do -fprofile-generate, run the instrumented binary and then -fprofile-use.
next prev parent reply other threads:[~2024-05-14 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 9:34 [Bug target/114412] New: [14 " pheeck at gcc dot gnu.org
2024-03-21 9:44 ` [Bug target/114412] " rguenth at gcc dot gnu.org
2024-03-22 12:35 ` law at gcc dot gnu.org
2024-05-07 7:45 ` [Bug target/114412] [14/15 " rguenth at gcc dot gnu.org
2024-05-13 10:55 ` tnfchris at gcc dot gnu.org
2024-05-14 8:50 ` pheeck at gcc dot gnu.org [this message]
2024-05-16 17:09 ` tnfchris at gcc dot gnu.org
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=bug-114412-4-0PMvr8r2kk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).