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 646D0395B44E; Wed, 16 Nov 2022 15:52:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 646D0395B44E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668613944;
	bh=nrYzOqK4tLYq1rFiUK/rVKcoC0uJLmgq2UkH9Ih9rWA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Jj4AdpVcUpAlxagLdFrgZe2hogkk0zzoiLQuncs4ZbfbQrfBgzRjpYzVD+zcxXaq+
	 CXF74IlpZ+2FKSbbd1gzXeafh3lJlHoSpmTKZXd9VO7l8LMjZTm2q2zhNUTHSMOGvV
	 Xc+pOjYKmbTDoGjzpqflZB10418xs1SoNcuVyMmY=
From: "kevin.bracey at alifsemi dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107714] MVE: Invalid addressing mode generated for VLD2
Date: Wed, 16 Nov 2022 15:52:24 +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: 12.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kevin.bracey at alifsemi 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: <bug-107714-4-vyqg9MDvVq@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 #1 from Kevin Bracey <kevin.bracey at alifsemi dot com> ---
Looking at that assembly output from Compiler Explorer, I'm also at a loss =
as
to what happened to the "6" for the VMUL. Maybe something else to look at?=