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 tree-optimization/106809] [12/13 regression] large bison grammars compilation got a lot slower, mainly due to -Wuninitialized
Date: Fri, 02 Sep 2022 07:04:05 +0000	[thread overview]
Message-ID: <bug-106809-4-YzC6ER3KEY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106809-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[12 regression] large bison |[12/13 regression] large
                   |grammars compilation got a  |bison grammars compilation
                   |lot slower, mainly due to   |got a lot slower, mainly
                   |-Wuninitialized             |due to -Wuninitialized
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
           Keywords|needs-bisection             |
             Status|NEW                         |ASSIGNED

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Also with GCC 13.  The obvious candidate would be the VN run done now to
identify unreachable code and reduce false positives.  I'll refactor timevars
to better track that.

OK, so callgrind points at dominated_by_p_w_unex, called from
rpo_elim::eliminate_avail.  Looks like we manage to run into a
degenerate case of a value with a very large avail set.  The
most avail queries are from

      if (eliminate && ! iterate)
        ...
      else
        /* If not eliminating, make all not already available defs
           available.  */
        FOR_EACH_SSA_TREE_OPERAND (op, gsi_stmt (gsi), i, SSA_OP_DEF)
          if (! avail.eliminate_avail (bb, op))
            avail.eliminate_push_avail (bb, op);

  parent reply	other threads:[~2022-09-02  7:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 23:42 [Bug ipa/106809] New: [12 " andres at anarazel dot de
2022-09-02  6:42 ` [Bug tree-optimization/106809] " rguenth at gcc dot gnu.org
2022-09-02  7:04 ` rguenth at gcc dot gnu.org [this message]
2022-09-02  7:12 ` [Bug tree-optimization/106809] [12/13 " rguenth at gcc dot gnu.org
2022-09-02  7:16 ` marxin at gcc dot gnu.org
2022-09-02  8:31 ` rguenth at gcc dot gnu.org
2022-09-02  8:32 ` rguenth at gcc dot gnu.org
2022-09-02 11:44 ` rguenth at gcc dot gnu.org
2022-09-02 12:13 ` rguenth at gcc dot gnu.org
2022-09-02 12:33 ` cvs-commit at gcc dot gnu.org
2022-09-02 12:33 ` [Bug tree-optimization/106809] [12 " rguenth at gcc dot gnu.org
2022-09-09  9:49 ` cvs-commit at gcc dot gnu.org
2022-09-09  9:50 ` rguenth at gcc dot gnu.org
2023-02-07 12:00 ` cvs-commit at gcc dot gnu.org
2023-02-07 12:33 ` 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-106809-4-YzC6ER3KEY@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).