From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 323D5384AB55; Mon, 24 Jun 2024 20:51:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 323D5384AB55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1719262313; bh=0CRTrrPwt1D+/Puk32gRelaSvPStudkdCaWFX68wfSY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AfjrSWngU44mcCZhRwnNvrn8BXdoYGiHbYtQp/AzKWoSYYD/oMDRAP/Uv96Suu03+ LszvJWbVPEEVz+dczJKTmtj2Sayg7BoKD2UW82DQPlY9H023NL/SnfZUSpesAT/XPl 3rcOeZCOe/iuSoGdPDTAnCl5Swmj+5D+fyY0yCac= From: "rsandifo at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115478] [15 Regression] gcc.target/aarch64/bitint-args.c fails since r15-1120-g2277f987979445 Date: Mon, 24 Jun 2024 20:51:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rsandifo at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: law at gcc dot gnu.org X-Bugzilla-Target-Milestone: 15.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D115478 Richard Sandiford changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org --- Comment #5 from Richard Sandiford --- How about adding a new match_operator predicate to common.md for this kind = of situation? It would be nice if it could automatically detect when the two operands have no nonzero bits in common, but doing that would need some refactoring of the nonzero_bits code, to ensure that the predicate gives a consistent result (and does that without polluting the current nonzero_bits cache). In the meantime, it might be enough to say that the insn must enforce the non-overlapping bits check itself.=