From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DBE843858D33; Wed, 22 Nov 2023 00:56:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DBE843858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1700614607; bh=Zty+W2XZ64wkxlXSSjsw0Ft5fsmBE9mb8gIV56oU8DA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TDSZzAFwthgjd+4MCRStP7ihYDwnvUQ+WnydrvZ9C8q9Z5wxGqlr2AfblCYZVD7ap fyxxuQhLgj71411NfKNWB7rVRZMlAHjCoETY5cVW4O/OrI6yFnQGUO/aW6ex/hWY0t KpGTfKhhr8KcftC7qLCisnyWTL+Z1YKmuxl1MpKY= From: "goon.pri.low at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112664] missed-optimization: extra comparison when reordering statements Date: Wed, 22 Nov 2023 00:56:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 13.2.1 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: goon.pri.low at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112664 --- Comment #4 from gooncreeper --- (In reply to Andrew Pinski from comment #1) > Dup. >=20 > *** This bug has been marked as a duplicate of bug 105496 *** Apologies. Though, how are you so good at finding duplicates? What's the secret?(In re= ply to Andrew Pinski from comment #3) > (In reply to gooncreeper from comment #2) > > Though, how are you so good at finding duplicates? What's the secret? >=20 > Everyone says I have bugzilla memorized but I don't, I am just really code > at doing keyword searches and knowing what keywords to search for. In this > case I searched for "canonical compare" because I knew this was a > canonicalization issue with how GCC changed `v < 6` into `v <=3D 5` Ah, if I knew the fancy names of optimizations I would probably be a bit be= tter at checking my finds.=