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 ipa/103585] fatigue2 requires inlining of peridida to work well
Date: Tue, 07 Dec 2021 10:17:47 +0000	[thread overview]
Message-ID: <bug-103585-4-qfxAuBdayx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103585-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Quick counting from gcov data.  It is 585898984 calls and from the disassmebly
the call is 101 instructions, so it account 58589898400
The perf reports shows 69059173576 difference so at least instruction count
wise most of it is call overhead of perdida.

  parent reply	other threads:[~2021-12-07 10:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 16:59 [Bug tree-optimization/103585] New: " hubicka at gcc dot gnu.org
2021-12-06 17:15 ` [Bug tree-optimization/103585] " hubicka at gcc dot gnu.org
2021-12-07  9:31 ` [Bug ipa/103585] " hubicka at gcc dot gnu.org
2021-12-07  9:49 ` hubicka at gcc dot gnu.org
2021-12-07 10:10 ` hubicka at gcc dot gnu.org
2021-12-07 10:17 ` hubicka at gcc dot gnu.org [this message]
2021-12-07 10:24 ` marxin at gcc dot gnu.org
2021-12-08 18:24 ` hubicka at gcc dot gnu.org
2021-12-08 18:28 ` hubicka at gcc dot gnu.org
2021-12-08 18:43 ` hubicka at gcc dot gnu.org
2021-12-12  8:43 ` hubicka at gcc dot gnu.org
2021-12-14 15:51 ` cvs-commit at gcc dot gnu.org
2022-01-31 10:33 ` hubicka at gcc dot gnu.org
2022-12-14  0:05 ` cvs-commit at gcc dot gnu.org
2023-01-19 13:21 ` jamborm at gcc dot gnu.org
2023-01-29  2:23 ` 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-103585-4-qfxAuBdayx@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).