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/108523] [13 Regression] -O1 -fcode-hoisting causes long compilation time ?
Date: Wed, 25 Jan 2023 12:37:41 +0000 [thread overview]
Message-ID: <bug-108523-4-U2Fu2R8AKH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108523-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:c29d85359add807200a1a851026b4e4a9d6b714c
commit r13-5348-gc29d85359add807200a1a851026b4e4a9d6b714c
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jan 25 13:31:46 2023 +0100
tree-optimization/108523 - fix endless iteration in VN
The following fixes not converging iteration in value-numbering of
PHI nodes when we use an equivalence to prove the PHI node is
degenerate. We have to avoid the situation where we oscillate
between the two equivalent values because the result is fed back
via a backedge.
PR tree-optimization/108523
* tree-ssa-sccvn.cc (visit_phi): Avoid using the exclusive
backedge value for the result when using predication to
prove equivalence.
next prev parent reply other threads:[~2023-01-25 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 17:00 [Bug c/108523] New: " dcb314 at hotmail dot com
2023-01-24 17:04 ` [Bug tree-optimization/108523] " dcb314 at hotmail dot com
2023-01-24 17:29 ` dcb314 at hotmail dot com
2023-01-24 17:42 ` dcb314 at hotmail dot com
2023-01-24 18:00 ` dcb314 at hotmail dot com
2023-01-24 18:25 ` dcb314 at hotmail dot com
2023-01-24 18:40 ` dcb314 at hotmail dot com
2023-01-24 18:56 ` dcb314 at hotmail dot com
2023-01-24 19:41 ` dcb314 at hotmail dot com
2023-01-24 19:49 ` [Bug tree-optimization/108523] [13 Regression] " pinskia at gcc dot gnu.org
2023-01-25 7:35 ` rguenth at gcc dot gnu.org
2023-01-25 10:06 ` rguenth at gcc dot gnu.org
2023-01-25 11:19 ` rguenth at gcc dot gnu.org
2023-01-25 12:31 ` rguenth at gcc dot gnu.org
2023-01-25 12:37 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-25 12:38 ` rguenth at gcc dot gnu.org
2023-01-25 16:49 ` dcb314 at hotmail dot com
2023-01-25 17:10 ` dcb314 at hotmail dot com
2023-01-26 7:21 ` rguenth at gcc dot gnu.org
2023-01-26 7:39 ` cvs-commit at gcc dot gnu.org
2023-01-26 7:40 ` rguenth 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-108523-4-U2Fu2R8AKH@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).