From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Jan Hubicka via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rep.dot.nop@gmail.com, Jan Hubicka <hubicka@kam.mff.cuni.cz>
Subject: Re: Improve -fprofile-report
Date: Fri, 3 Dec 2021 09:37:54 +0100 [thread overview]
Message-ID: <20211203093754.73999203@nbbrfq> (raw)
In-Reply-To: <20211127155632.GB25962@kam.mff.cuni.cz>
On Sat, 27 Nov 2021 16:56:32 +0100
Jan Hubicka via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> --- a/gcc/cfghooks.h
> +++ b/gcc/cfghooks.h
> @@ -36,22 +36,25 @@ along with GCC; see the file COPYING3. If not see
> and one CFG hook per CFG mode. */
> struct profile_record
> {
> - /* Likewise for a basic block's successors. */
> - int num_mismatched_count_out;
> - /* A weighted cost of the run-time of the function body. */
> - gcov_type_unsigned time;
> /* A weighted cost of the size of the function body. */
> int size;
> /* True iff this pass actually was run. */
> bool run;
> + bool fdo;
> };
>
fdo seems to be unused, does it belong to some other patch?
thanks,
prev parent reply other threads:[~2021-12-03 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 15:56 Jan Hubicka
2021-11-29 9:11 ` Martin Liška
2021-12-03 9:28 ` Jan Hubicka
2021-12-09 10:01 ` Martin Liška
2021-12-03 8:37 ` Bernhard Reutner-Fischer [this message]
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=20211203093754.73999203@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@kam.mff.cuni.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).