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/106570] [12/13 Regression] DCE sometimes fails with depending if statements since r12-2305-g398572c1544d8b75 Date: Tue, 09 Aug 2022 13:28:21 +0000 [thread overview] Message-ID: <bug-106570-4-OrR9L99WFb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106570 --- Comment #2 from Andrew Macleod <amacleod at redhat dot com> --- I think this is a duplicate of PR106379 . At the VRP2 stage I see: <bb 2> [local count: 1073741824]: if (c_6(D) == s_7(D)) goto <bb 3>; [34.00%] else goto <bb 5>; [66.00%] <bb 3> [local count: 365072224]: _1 = ~c_6(D); _2 = _1 & s_7(D); if (_2 != 0) goto <bb 4>; [75.00%] else goto <bb 5>; [25.00%] <bb 4> [local count: 628138969]: DCEMarker0_ (); <bb 5> [local count: 1073741824]: return; Which is basically the identical sequence.. it just took longer to get to it :-) We aren't removing this yet with ranger as I need to get to integrate rangers relation oracle with the simplifier so that it will see that _2 = ~s_7 & s_7.
next prev parent reply other threads:[~2022-08-09 13:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 11:35 [Bug tree-optimization/106570] New: DCE sometimes fails with depending if statements tmayerl at student dot ethz.ch 2022-08-09 13:15 ` [Bug tree-optimization/106570] [12/13 Regression] DCE sometimes fails with depending if statements since r12-2305-g398572c1544d8b75 marxin at gcc dot gnu.org 2022-08-09 13:28 ` amacleod at redhat dot com [this message] 2022-08-09 13:48 ` rguenth at gcc dot gnu.org 2022-08-10 13:53 ` rguenth at gcc dot gnu.org 2023-03-11 17:07 ` pinskia at gcc dot gnu.org 2023-03-14 13:16 ` marxin at gcc dot gnu.org 2023-05-08 12:25 ` [Bug tree-optimization/106570] [12/13/14 " rguenth at gcc dot gnu.org 2023-07-13 18:38 ` 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-106570-4-OrR9L99WFb@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).