From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E4C983858D37; Thu, 3 Feb 2022 23:17:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E4C983858D37 From: "gabravier at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104375] New: [x86] Failure to recognize bzhi patter nwhen shr is present Date: Thu, 03 Feb 2022 23:17:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gabravier at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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, 03 Feb 2022 23:18:00 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104375 Bug ID: 104375 Summary: [x86] Failure to recognize bzhi patter nwhen shr is present Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- #include uint64_t bextr_u64(uint64_t w, unsigned off, unsigned int len) { return (w >> off) & ((1U << len) - 1U); } With -mbmi2, this can be optimized to using shrx followed by bzhi. This transformation is done by LLVM, but not by GCC. PS: Even in the case where the shr is removed and thus the bzhi pattern is recognized (e.g. `return w & ((1U << len) - 1U);`), it is still not compiled optimally as it for some reason decides to put the result of the bzhi in an intermediary register before moving it to eax.=