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 579A63894C0F; Wed,  2 Sep 2020 14:08:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 579A63894C0F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1599055713;
 bh=sOcrgASet/gEb32iw009Mqj/h9jdrX79pMHnTERpKGU=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=t5RRpoIQ3YUA9L5XrYaYOBAYt7CJ1E5bfAApb0MmiOsHyYpktigCjclNMQhEmpdzd
 KlQ1Oblq7LZVFb1zKsykepRXzG/kPoXxNdeDmF9ujsPeukEA3a9bY5RIJfcPOy8syH
 nCTx2v33NCcRJdTRU4PDpd0aFx1dYy4z5eLNr4Uc=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96895] ABI of returning V1DF differs between GCC and clang
Date: Wed, 02 Sep 2020 14:08:33 +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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
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-96895-4-orSMoizBRT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96895-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96895-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2020 14:08:33 -0000

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Michael Matz from comment #2)
> The psABI doesn't say anything about such types, no.  Maybe it could in s=
ome
> additional info pages, but it's always a problem to codify behaviour
> retroactively
> in it, when conflicting implementations already exist.  It is about
> extension types, though, so we might be fine.
>=20
> FWIW, even ignoring the obvious relation of v1Xf to Xf, GCC behaviour for
> float and clang behaviour for double is the most logical one: this extend=
ed
> type is most
> similar to a struct containing one float/double, and such are passed in X=
MM
> registers per psABI.  As this is also consistent with how a single
> top-level float is passed, this choice is the most consistent one.  This =
is
> also
> what the psABI _would_ say, if we had written it into it, so at least both
> compilers would need a change to implement it.

So vector types with element type T and N, a power-of-two, not otherwise
specified are passes the same as

struct S { T a[N] };

?  I guess there's mismatch then for AVX types with -mno-avx then at least
(AVX512 are probably too big to be passed in registers).=