public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Tue, 09 May 2023 19:58:39 +0000 [thread overview]
Message-ID: <bug-109447-4-lVbxCiOpar@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109447-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109447
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:0069ce6631880776a44fb8408c6428c0812285cf
commit r12-9526-g0069ce6631880776a44fb8408c6428c0812285cf
Author: Dan Horák <dan@danny.cz>
Date: Wed May 3 14:29:09 2023 -0500
libffi: 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.
Merged from upstream libffi commit:
464b4b66e3cf3b5489e730c1466ee1bf825560e0
2023-05-03 Dan Horák <dan@danny.cz>
libffi/
PR libffi/109447
* src/powerpc/ffi_linux64.c (ffi_prep_args64): Update arg.f128
pointer.
(cherry picked from commit 043550bceea7881163bba5d8a0486bb100a05809)
prev parent reply other threads:[~2023-05-09 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 17:48 [Bug libffi/109447] New: " seurer at gcc dot gnu.org
2023-04-07 18:53 ` [Bug libffi/109447] " schwab@linux-m68k.org
2023-04-08 3:21 ` bergner at gcc dot gnu.org
2023-04-08 3:36 ` bergner at gcc dot gnu.org
2023-04-08 15:37 ` bergner at gcc dot gnu.org
2023-04-08 15:37 ` bergner at gcc dot gnu.org
2023-04-08 16:14 ` segher at gcc dot gnu.org
2023-04-08 18:00 ` bergner at gcc dot gnu.org
2023-05-06 15:31 ` cvs-commit at gcc dot gnu.org
2023-05-06 20:59 ` cvs-commit at gcc dot gnu.org
2023-05-09 19:58 ` cvs-commit at gcc dot gnu.org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109447-4-lVbxCiOpar@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).