public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106809] [12 regression] large bison grammars compilation got a lot slower, mainly due to -Wuninitialized
Date: Tue, 07 Feb 2023 12:00:39 +0000 [thread overview]
Message-ID: <bug-106809-4-ZmvJNNDg4Z@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
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:5125737077adc2110b9f17f06141e8f76ccab9b9
commit r11-10510-g5125737077adc2110b9f17f06141e8f76ccab9b9
Author: Richard Biener <rguenther@suse.de>
Date: Fri Sep 2 13:36:13 2022 +0200
tree-optimization/106809 - compile time hog in VN
The dominated_by_p_w_unex function is prone to high compile time.
With GCC 12 we introduced a VN run for uninit diagnostics which now
runs into a degenerate case with bison generated code. Fortunately
this case is easy to fix with a simple extra check - a more
general fix needs more work.
PR tree-optimization/106809
* tree-ssa-sccvn.c (dominaged_by_p_w_unex): Check we have
more than one successor before doing extra work.
* gcc.dg/torture/pr106809.c: New testcase.
(cherry picked from commit be1b42de9c151d46c89f9a8f82d4c5839a19ea94)
next prev parent reply other threads:[~2023-02-07 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 23:42 [Bug ipa/106809] New: " 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 ` [Bug tree-optimization/106809] [12/13 " rguenth at gcc dot gnu.org
2022-09-02 7:12 ` 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 [this message]
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-ZmvJNNDg4Z@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).