public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110004] large increase in profile mismatches on tramp3d
Date: Sat, 01 Jul 2023 22:13:34 +0000	[thread overview]
Message-ID: <bug-110004-4-9aG1keZ3GL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110004-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110004

--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Linkes the statistics for outedges (that probabilities sums to 100).
Here are statistic for inedges.

We track mismatches after alignments RTL pass since it is last one, so it
cummulates all the mismatches through the pipeline. Martin was objecting agains
tracing all the passes independently.

https://lnt.opensuse.org/db_default/v4/CPP/graph?highlight_run=42409&plot.0=353.964.7

  parent reply	other threads:[~2023-07-01 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 15:30 [Bug middle-end/110004] New: " hubicka at gcc dot gnu.org
2023-05-30  7:46 ` [Bug middle-end/110004] " rguenth at gcc dot gnu.org
2023-07-01 22:13 ` hubicka at gcc dot gnu.org [this message]
2023-07-02  8:25 ` hubicka 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-110004-4-9aG1keZ3GL@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).