From: Richard Henderson <rth@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: libffi 3.2 and disruptive changes
Date: Wed, 12 Nov 2014 07:22:00 -0000 [thread overview]
Message-ID: <54630ABA.6030804@redhat.com> (raw)
In-Reply-To: <20141112071646.GA14344@linux.vnet.ibm.com>
On 11/12/2014 08:16 AM, Dominik Vogt wrote:
> On Tue, Nov 11, 2014 at 09:53:35AM -0500, Anthony Green wrote:
>> I'd like to move ahead with Richard's proposed changes for GO, complex
>> types, and the numerous other clean ups he's proposed.
>
> Richard proposed fixes for complex types? Can you point me to the
> messages with these patches please? I must have overlooked them.
They're mixed in with the Go closures patch sets, since we will
of course want libgo to make use of this new complex support.
Which will fix, e.g.
> case GO_COMPLEX64:
> #ifdef __alpha__
> runtime_throw("the libffi library does not support Complex64 type with "
> "reflect.Call or runtime.SetFinalizer");
r~
prev parent reply other threads:[~2014-11-12 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 14:53 Anthony Green
2014-11-11 14:59 ` James Greenhalgh
2014-11-12 12:04 ` Anthony Green
2014-11-11 15:01 ` Alan Lawrence
2014-11-12 7:16 ` Dominik Vogt
2014-11-12 7:22 ` Richard Henderson [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=54630ABA.6030804@redhat.com \
--to=rth@redhat.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).