From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5BD17385842A; Mon, 3 Jan 2022 09:50:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5BD17385842A From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66502] SCCVN can't handle PHIs optimistically optimally Date: Mon, 03 Jan 2022 09:50:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cf_known_to_work bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2022 09:50:35 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66502 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Known to work| |10.3.1 Status|ASSIGNED |RESOLVED --- Comment #6 from Richard Biener --- (In reply to Andrew Pinski from comment #5) > (In reply to Richard Biener from comment #4) > > SCCVN preference changed. Missed optimization remains (now the other > > variant). >=20 > GCC 10 looks like it can handle both now. I don't know if that means this > can be marked as fixed though. So it looks like we now first value-number j to a (backedge not executable) and in the second iteration (backedge executable) we value-number it to i. I guess the special-casing of a single executable edge makes this work now and also ensure we don't oscillate between both choices.=