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/106379] DCE depends on order Date: Thu, 21 Jul 2022 11:23:43 +0000 [thread overview] Message-ID: <bug-106379-4-TrqjAVBilj@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- With that, what remains looks like a VRP/ranger issue though. Good: <bb 2> [local count: 1073741824]: _1 = ~c_4(D); if (c_4(D) == s_5(D)) goto <bb 3>; [34.00%] else goto <bb 5>; [66.00%] <bb 3> [local count: 365072224]: _2 = _1 & s_5(D); if (_2 != 0) goto <bb 4>; [33.00%] else goto <bb 5>; [67.00%] <bb 4> [local count: 120473833]: DCEMarker0_ (); <bb 5> [local count: 1073741824]: Bad: <bb 2> [local count: 1073741824]: if (s_4(D) == c_5(D)) goto <bb 3>; [34.00%] else goto <bb 5>; [66.00%] <bb 3> [local count: 365072224]: _1 = ~c_5(D); _2 = _1 & s_4(D); if (_2 != 0) goto <bb 4>; [33.00%] else goto <bb 5>; [67.00%] <bb 4> [local count: 120473833]: DCEMarker0_ (); <bb 5> [local count: 1073741824]: the difference is just the point of definition of _1.
next prev parent reply other threads:[~2022-07-21 11:23 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 [this message] 2022-07-21 11:24 ` cvs-commit at gcc dot gnu.org 2022-08-08 20:36 ` amacleod at redhat dot com 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-TrqjAVBilj@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).