From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 57F1E3858D20; Mon, 27 Feb 2023 11:00:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57F1E3858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677495608; bh=hnV/DPvTXCDT6angl0iwl3Uh4MWTl87L7Nl9bfVFpnw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mKMcHSSr7rvXYYsmddusgjfeEp3ZV9+mfWu6I7OopEfPyO4KMI0+cdNXPG/xCwuld EB4ZfaPUqyJk7/+HWUV2svMWuEXql0kLlrB5AmcP2UP/oFXZaI8S3CoUqrcp9Kr1C4 eP70hIH11pl+FUUA4lTXQCrDTTd3DXPynOpLuXGo= From: "jbeulich at suse dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108941] Error: operand type mismatch for `shr' with binutils master Date: Mon, 27 Feb 2023 11:00:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jbeulich at suse 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: 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=3D108941 --- Comment #7 from jbeulich at suse dot com --- Maybe what would help is a discussion in the context of the binutils patch, despite it already having been committed. As said there and earlier here, t= here may be reasons to adjust (back) some of what it did, but there needs to be a sufficiently consistent pattern behind that and at least RCL/RCR, according= to whichever pattern, have to remain unsigned-only.=