public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: libffi-discuss@sourceware.org
Subject: [PING][RFC][PATCH 0/3] Complex type support (FFI_TYPE_COMPLEX)
Date: Wed, 20 Aug 2014 06:57:00 -0000	[thread overview]
Message-ID: <20140820065718.GA2818@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140722092734.GA23937@linux.vnet.ibm.com>

Ping.

On Tue, Jul 22, 2014 at 10:27:34AM +0100, Dominik Vogt wrote:
> 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).
> 
> Complex support in libffi is necessary to support the complex
> types with the reflection interface of the libgo of the Go
> programming language (gccgo).
> 
> * Patch 1/3: Somewhat reduce the macro hell.
> 
> This is a general cleanup patch that reduces the complexity of
> some preprocessor macros.  It is not strictly necessary, but it
> simplifies the following patch.
> 
> * Patch 2/3: FFI_TYPE_COMPLEX framework
> 
> The patch introducing the FFI_TYPE_COMPLEX framework, including
> documentation and test cases.  Note that the patch introduces
> predefined ffi_types for complex float, complex double and complex
> longdouble but also supports the non-standard complex types that
> gcc supports (the ffi_types have to be defined manually for them).
> (See documentation for details.)
> 
> * Patch 3/3: S390: Implement FFI_TYPE_COMPLEX
> 
> A simple patch that implements the s390-abi for complex types.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt
IBM Germany

  parent reply	other threads:[~2014-08-20  6:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  9:27 [RFC][PATCH " 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 ` Dominik Vogt [this message]
2014-09-20 10:31 ` [RFC][PATCH 0/3] " Anthony Green
2014-09-29 10:24   ` 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=20140820065718.GA2818@linux.vnet.ibm.com \
    --to=vogt@linux.vnet.ibm.com \
    --cc=libffi-discuss@sourceware.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).