public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107060] -fanalyzer unbearably slow when compiling GNU Emacs
Date: Tue, 27 Sep 2022 22:22:28 +0000	[thread overview]
Message-ID: <bug-107060-4-dbArdF2aOm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107060-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
perf shows that 64% of the time is taken by this ctor:
  shortest_paths<ana::eg_traits, ana::exploded_path>::shortest_paths

  parent reply	other threads:[~2022-09-27 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 19:20 [Bug analyzer/107060] New: " eggert at cs dot ucla.edu
2022-09-27 20:55 ` [Bug analyzer/107060] " dmalcolm at gcc dot gnu.org
2022-09-27 21:31 ` dmalcolm at gcc dot gnu.org
2022-09-27 22:22 ` dmalcolm at gcc dot gnu.org [this message]
2022-09-28 13:57 ` dmalcolm at gcc dot gnu.org
2022-09-28 15:01 ` dmalcolm at gcc dot gnu.org
2022-09-29  8:10 ` rguenth at gcc dot gnu.org
2022-10-05 17:54 ` cvs-commit at gcc dot gnu.org
2022-10-05 18:20 ` dmalcolm at gcc dot gnu.org
2023-03-02 18:26 ` dmalcolm 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-107060-4-dbArdF2aOm@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).