public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/41908] closures fail for some structure arguments containing floats
Date: Fri, 04 Dec 2009 18:42:00 -0000	[thread overview]
Message-ID: <20091204184219.19327.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41908-3831@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from uros at gcc dot gnu dot org  2009-12-04 18:42 -------
Subject: Bug 41908

Author: uros
Date: Fri Dec  4 18:41:59 2009
New Revision: 154988

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=154988
Log:
        PR libffi/41908
        * src/x86/ffi64.c (classify_argument): Update from
        gcc/config/i386/i386.c.
        (ffi_closure_unix64_inner): Do not use the address of two consecutive
        SSE registers directly.
        * testsuite/libffi.call/cls_dbls_struct.c (main): Remove xfail
        for x86_64 linux targets.


Modified:
    trunk/libffi/ChangeLog
    trunk/libffi/src/x86/ffi64.c
    trunk/libffi/testsuite/libffi.call/cls_dbls_struct.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41908


  parent reply	other threads:[~2009-12-04 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 15:55 [Bug libffi/41908] New: " rfm at gnu dot org
2009-11-02 15:58 ` [Bug libffi/41908] " rfm at gnu dot org
2009-11-02 21:18 ` andreast at gcc dot gnu dot org
2009-11-02 21:19 ` andreast at gcc dot gnu dot org
2009-11-03 17:47 ` pinskia at gcc dot gnu dot org
2009-11-12 11:48 ` rfm at gnu dot org
2009-12-03 20:40 ` ubizjak at gmail dot com
2009-12-03 21:05 ` ubizjak at gmail dot com
2009-12-04 18:42 ` uros at gcc dot gnu dot org [this message]
2009-12-04 18:44 ` ubizjak at gmail dot com

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=20091204184219.19327.qmail@sourceware.org \
    --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).