public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1946] profile: do not collect stats unless TDF_DETAILS Date: Wed, 3 Aug 2022 08:56:46 +0000 (GMT) [thread overview] Message-ID: <20220803085646.F0CC43857418@sourceware.org> (raw) https://gcc.gnu.org/g:7585e5ecb47761516b8f397002819f2c95b8c32e commit r13-1946-g7585e5ecb47761516b8f397002819f2c95b8c32e Author: Martin Liska <mliska@suse.cz> Date: Wed Aug 3 10:53:22 2022 +0200 profile: do not collect stats unless TDF_DETAILS gcc/ChangeLog: * profile.cc (compute_branch_probabilities): Do not collect stats unless TDF_DETAILS. Diff: --- gcc/profile.cc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/gcc/profile.cc b/gcc/profile.cc index 92de821b8bb..96121d60711 100644 --- a/gcc/profile.cc +++ b/gcc/profile.cc @@ -753,7 +753,8 @@ compute_branch_probabilities (unsigned cfg_checksum, unsigned lineno_checksum) bb->count = profile_count::from_gcov_type (bb_gcov_count (bb)); else bb->count = profile_count::guessed_zero (); - if (dump_file && bb->index >= 0) + + if (dump_file && (dump_flags & TDF_DETAILS) && bb->index >= 0) { double freq1 = cnt.to_sreal_scale (old_entry_cnt).to_double (); double freq2 = bb->count.to_sreal_scale @@ -776,8 +777,8 @@ compute_branch_probabilities (unsigned cfg_checksum, unsigned lineno_checksum) nsum2 += stat.feedback; fprintf (dump_file, " Basic block %4i guessed freq: %12.3f" - " cummulative:%6.2f%% " - " feedback freq: %12.3f cummulative:%7.2f%%" + " cumulative:%6.2f%% " + " feedback freq: %12.3f cumulative:%7.2f%%" " cnt: 10%" PRId64 "\n", stat.bb->index, stat.guessed, nsum1 * 100 / sum1,
reply other threads:[~2022-08-03 8:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220803085646.F0CC43857418@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).