From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5C62E3858C2C; Thu, 14 Oct 2021 00:49:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5C62E3858C2C From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102738] Failure to optimize right shift of 32-bit int after it's already been shifted by 31 Date: Thu, 14 Oct 2021 00:49:26 +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: 12.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: bug_status cf_reconfirmed_on short_desc everconfirmed 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: Thu, 14 Oct 2021 00:49:26 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102738 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-10-14 Summary|Failure to optimize right |Failure to optimize right |shift of 128-bit value |shift of 32-bit int after |after it's already been |it's already been shifted |shifted by 127 |by 31 Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski --- GCC does not even do the int case: int a(int f, int g) { return (f >> 31) >> g; } Actually this can be simplified down to this really (which clang does not handle but handles a simular case; see below): int a(int f, int g) { if (f =3D=3D 0 || f =3D=3D -1) return f >> g; __builtin_unreachable(); } This should just return f here :). Basically if GCC knows f is already 0 or -1, then f shifted by any value is still f. clang is able to handle this case though int a1(int f, int g) { if (f =3D=3D 0 || f =3D=3D 1) return (-f) >> g; __builtin_unreachable(); }=