From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4709E385380F; Mon, 10 Oct 2022 16:00:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4709E385380F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665417604; bh=EPIYnHsy4TeuufK9xHQYAJkyZVTaS6tgU2hM3oNYqTk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZKMqS7ULm4bWodbuoCynvqx9dxT23GzBWjm+BGMOpNPggtmJ/P5/ryBssyCDkZVNU kSurxw/LvccIXOx+uap3pxgELsPjPDCmfDS0Pdw92OasNdEGY7GbwVlERElo9ESMrU XlKBcSmw+WarHRytIktBTisf/qw0Am0iKm9hCCHI= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98519] rs6000: @pcrel unsupported on this instruction error in pveclib Date: Mon, 10 Oct 2022 16:00:02 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher 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=3D98519 --- Comment #32 from Segher Boessenkool --- (In reply to Peter Bergner from comment #31) > (In reply to Segher Boessenkool from comment #30) > > We have to disallow all (*all*) operands that require prefixed insns, u= ntil > > we can handle those properly. >=20 > So if we can't disallow pcrel addresses in asm operands in=20 > rs6000_legitimate_address_p, then where can we disallow them when they're > used with all of the current memory constraints? Ie, not the new pcrel > address friendly constraint we don't have yet? Maybe we can do something like "m!"(xx) to mean prefixed addressing is allowed. This would be handled adjacent to where we handle "m<>" already (in recog.cc mostly).=