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/100053] [9/10/11 Regression] tree-fre incorrectly delete a condition Date: Tue, 13 Apr 2021 12:31:22 +0000 [thread overview] Message-ID: <bug-100053-4-tQENnCtEOp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100053-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100053 --- Comment #7 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:f9810422f6768b914aabfcbffe64f535bdd18452 commit r11-8152-gf9810422f6768b914aabfcbffe64f535bdd18452 Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 13 12:05:53 2021 +0200 tree-optimization/100053 - fix predication in VN This avoids doing optimistic dominance queries involving non-executable backedges when validating recorded predicated values in VN because we have no way to force re-evaluating validity when optimistically not executable edges become executable later. 2021-04-13 Richard Biener <rguenther@suse.de> PR tree-optimization/100053 * tree-ssa-sccvn.c (vn_nary_op_get_predicated_value): Do not use optimistic dominance queries for backedges to validate predicated values. (dominated_by_p_w_unex): Add parameter to ignore executable state on backedges. (rpo_elim::eliminate_avail): Adjust. * gcc.dg/torture/pr100053.c: New testcase. * gcc.dg/tree-ssa/ssa-fre-93.c: Likewise.
next prev parent reply other threads:[~2021-04-13 12:31 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-12 21:17 [Bug tree-optimization/100053] New: " qinzhao at gcc dot gnu.org 2021-04-12 22:52 ` [Bug tree-optimization/100053] " pinskia at gcc dot gnu.org 2021-04-13 8:19 ` rguenth at gcc dot gnu.org 2021-04-13 9:11 ` rguenth at gcc dot gnu.org 2021-04-13 10:12 ` rguenth at gcc dot gnu.org 2021-04-13 10:12 ` [Bug tree-optimization/100053] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-04-13 11:36 ` rguenth at gcc dot gnu.org 2021-04-13 12:31 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-13 12:31 ` [Bug tree-optimization/100053] [9/10 " rguenth at gcc dot gnu.org 2021-04-13 15:28 ` qinzhao at gcc dot gnu.org 2021-04-13 16:32 ` rguenther at suse dot de 2021-04-13 23:55 ` qinzhao at gcc dot gnu.org 2021-04-26 11:46 ` cvs-commit at gcc dot gnu.org 2021-05-04 13:54 ` [Bug tree-optimization/100053] [9 " cvs-commit at gcc dot gnu.org 2021-05-04 13:55 ` 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-100053-4-tQENnCtEOp@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: linkBe 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).