public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110489] Slow building virtual.c.i from p11-kit
Date: Fri, 30 Jun 2023 08:37:21 +0000	[thread overview]
Message-ID: <bug-110489-4-uHVDZrrNnf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110489-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
There would possibly be opportunity to optimize some of our infrastructure for
the case where we have 3 basic blocks (the minimum, ENTRY, bb2 and EXIT).  For
example dominance compute doesn't need to be "computed", the only special case
to consider is that EXIT is not reachable.

The testcase at hand seems to consist of forwarders.  In general single-BB
functions can be quite common in C++ code as well.  A lot of passes
could excuse themselves as well (next special case is BB2 having a
backedge to itself).  There is quite some constant overhead all over the place
even when we do nothing in the end.

  parent reply	other threads:[~2023-06-30  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 19:35 [Bug c/110489] New: " sjames at gcc dot gnu.org
2023-06-29 19:46 ` [Bug middle-end/110489] " pinskia at gcc dot gnu.org
2023-06-29 19:54 ` pinskia at gcc dot gnu.org
2023-06-30  7:45 ` rguenth at gcc dot gnu.org
2023-06-30  8:37 ` rguenth at gcc dot gnu.org [this message]
2023-06-30  8:38 ` cvs-commit 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-110489-4-uHVDZrrNnf@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).