public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106379] DCE depends on order Date: Mon, 08 Aug 2022 20:36:47 +0000 [thread overview] Message-ID: <bug-106379-4-ff6fHO1Df6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106379-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106379 --- Comment #4 from Andrew Macleod <amacleod at redhat dot com> --- Ranger actually appears to handle both cases the same. VRP1 gets it whilst ranger does not. I believe this to be because we are match and simplifying _1 = ~c_5(D); _2 = _1 & s_4(D); with c_5 == s_4... but at this point, the simplification code doesn't understand the relation oracle, so I beleive it to be missing the fact that _2 will evaluate to 0 because it doesnt see the equivalency. VRP1 gets it because its in intergrated in the legacy range that passed in as an equivset. I will shortly get to some equivalency processing during simplificatoin as a part of trying to remove VRP1. We should then pick this up with in EVRP.
next prev parent reply other threads:[~2022-08-08 20:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-21 9:13 [Bug c/106379] New: " tmayerl at student dot ethz.ch 2022-07-21 9:48 ` [Bug tree-optimization/106379] " rguenth at gcc dot gnu.org 2022-07-21 11:23 ` rguenth at gcc dot gnu.org 2022-07-21 11:24 ` cvs-commit at gcc dot gnu.org 2022-08-08 20:36 ` amacleod at redhat dot com [this message] 2023-05-18 17:26 ` pinskia at gcc dot gnu.org 2023-07-13 18:39 ` pinskia at gcc dot gnu.org 2023-09-17 5:46 ` pinskia 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-106379-4-ff6fHO1Df6@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).