From: Anthony Green <green@moxielogic.com>
To: vogt@linux.vnet.ibm.com
Cc: libffi-discuss@sourceware.org
Subject: Re: [RFC][PATCH 0/3] Complex type support (FFI_TYPE_COMPLEX)
Date: Sat, 20 Sep 2014 10:31:00 -0000 [thread overview]
Message-ID: <87y4teh9c6.fsf@moxielogic.com> (raw)
In-Reply-To: <20140722092734.GA23937@linux.vnet.ibm.com> (Dominik Vogt's message of "Tue, 22 Jul 2014 10:27:34 +0100")
Dominik Vogt <vogt@linux.vnet.ibm.com> writes:
> The following series of patches introduces a framework for C
> complex types (FFI_TYPE_COMPLEX) and support for complex types on
> s390/s390x. For now, an architecture that supports complex types
> has to define FFI_TARGET_HAS_COMPLEX_TYPE to activate the support.
> This can be changed in the future when most architecture have
> implemented it so that this is the default. The patch does not
> address complex support in java_raw_api.c (as there is no
> documentation how this interface is supposed to work).
Thank you for this tremendous effort, Dominik.
I'm not all that familiar with how GCC handles complex types on other
architectures, but hopefully they are as straight forward as on s390.
It would be nice if the complex test cases turned into expected failures
for platforms that don't have the back end support.
I've committed this patch to the libffi git repo.
AG
next prev parent reply other threads:[~2014-09-20 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 9:27 Dominik Vogt
2014-07-22 9:35 ` [RFC][PATCH 1/3] " Dominik Vogt
2014-07-23 8:41 ` Dominik Vogt
2014-07-22 9:36 ` [RFC][PATCH 3/3] " Dominik Vogt
2014-07-22 9:36 ` [RFC][PATCH 2/3] " Dominik Vogt
2014-09-23 13:17 ` Alan Lawrence
2014-08-20 6:57 ` [PING][RFC][PATCH 0/3] " Dominik Vogt
2014-09-20 10:31 ` Anthony Green [this message]
2014-09-29 10:24 ` [RFC][PATCH " Dominik Vogt
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=87y4teh9c6.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=vogt@linux.vnet.ibm.com \
/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).