From: "Martin Liška" <mliska@suse.cz>
To: Erick Ochoa <eochoa@gcc.gnu.org>,
Richard Biener <richard.guenther@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Creating a wrapper around a function at compile time
Date: Thu, 14 Jul 2022 16:10:14 +0200 [thread overview]
Message-ID: <90b22551-734c-72e4-ad33-864385162f9f@suse.cz> (raw)
In-Reply-To: <CAJ_nqzj-R8iooS2_h0ndEu_KVg4Wn=-2vM7V8cWHWn62SpTQtg@mail.gmail.com>
On 7/14/22 16:08, Erick Ochoa via Gcc wrote:
> Last time I checked, value profiling can only track a single value per
> statement.
Hi.
Take a look at HIST_TYPE_INDIR_CALL which we use for tracking at maximum 32
(#define GCOV_TOPN_MAXIMUM_TRACKED_VALUES 32) and we use for indirect call
speculative calls which you can see for instance here:
./gcc/testsuite/g++.dg/tree-prof/indir-call-prof.C
Cheers,
Martin
next prev parent reply other threads:[~2022-07-14 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 12:38 Erick Ochoa
2022-07-14 13:27 ` Richard Biener
2022-07-14 13:29 ` Richard Biener
2022-07-14 13:46 ` Erick Ochoa
2022-07-14 13:50 ` Richard Biener
2022-07-14 14:08 ` Erick Ochoa
2022-07-14 14:10 ` Martin Liška [this message]
2022-07-14 14:25 ` Erick Ochoa
2022-07-15 8:10 ` Martin Liška
2022-07-15 8:33 ` Erick Ochoa
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=90b22551-734c-72e4-ad33-864385162f9f@suse.cz \
--to=mliska@suse.cz \
--cc=eochoa@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).