From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id B5AEF3858426; Fri, 30 Dec 2022 11:25:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5AEF3858426
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1672399543;
	bh=E5bTnOQ2JcQSaAkniBnEpVSwfH2p03PFCgb56kTXnis=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YTTALU4Xv2bSIW7iJZ/Ub0Ahy/mY/+dutYHguuKQclovw1NwXn5j/MPdGBgbaXkba
	 W4AC5XEQiw4YgQ4n4aYpk61GVtjxqP+l5vVq4spa2eacZtBVVjnxal/H0B+Z93omJs
	 J85Bd/kATW+4KIetnpjM8OpekjOGSERh/7y4THtQ=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107714] MVE: Invalid addressing mode generated for VLD2
Date: Fri, 30 Dec 2022 11:25:42 +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: 13.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: <bug-107714-4-5pma6r1o0o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107714-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107714

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stam Markianos-Wright
<stammark@gcc.gnu.org>:

https://gcc.gnu.org/g:4269a6567eb991e6838f40bda5be9e3a7972530c

commit r13-4935-g4269a6567eb991e6838f40bda5be9e3a7972530c
Author: Stam Markianos-Wright <stam.markianos-wright@arm.com>
Date:   Fri Dec 30 11:25:22 2022 +0000

    Fix memory constraint on MVE v[ld/st][2/4] instructions [PR107714]

    In the M-Class Arm-ARM:

    https://developer.arm.com/documentation/ddi0553/bu/?lang=3Den

    these MVE instructions only have '!' writeback variant and at:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107714

    we found that the Um constraint would also allow through a
    register offset writeback, resulting in an assembler error.

    Here I have added a new constraint and predicate for these
    instructions, which (uniquely, AFAICT), only support a `!` writeback
    increment by the data size (inside the compiler this is a POST_INC).

    No regressions in arm-none-eabi with MVE and MVE.FP.

    gcc/ChangeLog:
            PR target/107714
            * config/arm/arm-protos.h (mve_struct_mem_operand): New protoyp=
e.
            * config/arm/arm.cc (mve_struct_mem_operand): New function.
            * config/arm/constraints.md (Ug): New constraint.
            * config/arm/mve.md (mve_vst4q<mode>): Change constraint.
            (mve_vst2q<mode>): Likewise.
            (mve_vld4q<mode>): Likewise.
            (mve_vld2q<mode>): Likewise.
            * config/arm/predicates.md (mve_struct_operand): New predicate.

    gcc/testsuite/ChangeLog:
            PR target/107714
            * gcc.target/arm/mve/intrinsics/vldst24q_reg_offset.c: New test=
.=