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 78CC03858D1E; Sat,  8 Apr 2023 03:36:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 78CC03858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1680924980;
	bh=DG9MtiHzl2SkHzE13QskMf9JqmNbRKWoJWSyzqBcRaw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=AW8f1eKCQlccarTKyxRtOyviRzh561mwzdzyPYacg8ZoS66YuXZ6Np2oWG3NFQsGm
	 QMTsRJ7c0gwlJ6z5PxNLam71EXBpJAzVdjHoRtfxy49R5CulZLbFY4UimidFC4jSO9
	 boOIwty2zkQOMnnQErRyt6liTbn6abUNL7QszS1o=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/109447] test case
 libffi.closures/cls_align_longdouble_split.c fails
Date: Sat, 08 Apr 2023 03:36:19 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 12.2.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner 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-109447-4-JgujtyA0On@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109447-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109447-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=3D109447

--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
Hmmm, libffi commit 464b4b66e3cf3b5489e730c1466ee1bf825560e0 seems to be
missing from GCC's sources.  I'll try applying that and see if it fixes the
problem.

commit 464b4b66e3cf3b5489e730c1466ee1bf825560e0
Author:     Dan Hor=C3=A1k <dan@danny.cz>
AuthorDate: Mon Jan 31 14:08:09 2022 +0100
Commit:     GitHub <noreply@github.com>
CommitDate: Mon Jan 31 08:08:09 2022 -0500

    powerpc64: fix handling of homogeneous float128 structs (#689)

    If there is a homogeneous struct with float128 members, they should be
    copied to vector register save area. The current code incorrectly copies
    only the value of the first member, not increasing the pointer with each
    iteration. Fix this.

Given the output Bill is seeing and the description of the git log entry, it
seems like this may be the culprit.=