* libffi 3.2 and disruptive changes
@ 2014-11-11 14:53 Anthony Green
2014-11-11 14:59 ` James Greenhalgh
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Anthony Green @ 2014-11-11 14:53 UTC (permalink / raw)
To: libffi-discuss
I'd like to move ahead with Richard's proposed changes for GO, complex
types, and the numerous other clean ups he's proposed.
These changes will break msvc builds as well as iOS/OSX.
As long as we're breaking things, I'd like to use this opportunity to
change the header files so we have a shared set of .h files in
/usr/include.
Once things settle down from these changes, I'm hoping somebody can help
with the msvc and iOS/OSX ports.
In preparation for all of these changes, I've made a quick 3.2 release.
There were a few nice fixes that were sitting around in the tree, and
I'm not sure how long this next round of hacking will take.
The 3.2 release should be in pretty good shape *except* for the win32/64
msvc builds which are known to be broken. See
https://github.com/atgreen/libffi/issues/138 for details.
Thanks,
AG
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: libffi 3.2 and disruptive changes
2014-11-11 14:53 libffi 3.2 and disruptive changes 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
2 siblings, 1 reply; 6+ messages in thread
From: James Greenhalgh @ 2014-11-11 14:59 UTC (permalink / raw)
To: Anthony Green; +Cc: libffi-discuss
On Tue, Nov 11, 2014 at 02:53:35PM +0000, 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.
>
> These changes will break msvc builds as well as iOS/OSX.
>
> As long as we're breaking things, I'd like to use this opportunity to
> change the header files so we have a shared set of .h files in
> /usr/include.
>
> Once things settle down from these changes, I'm hoping somebody can help
> with the msvc and iOS/OSX ports.
>
> In preparation for all of these changes, I've made a quick 3.2 release.
> There were a few nice fixes that were sitting around in the tree, and
> I'm not sure how long this next round of hacking will take.
>
> The 3.2 release should be in pretty good shape *except* for the win32/64
> msvc builds which are known to be broken. See
> https://github.com/atgreen/libffi/issues/138 for details.
AArch64 linux builds are still broken (Alan Lawrence posted a patch at
https://sourceware.org/ml/libffi-discuss/2014/msg00091.html )
Could we please have that patch in for the 3.2 release?
Thanks,
James
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libffi 3.2 and disruptive changes
2014-11-11 14:53 libffi 3.2 and disruptive changes Anthony Green
2014-11-11 14:59 ` James Greenhalgh
@ 2014-11-11 15:01 ` Alan Lawrence
2014-11-12 7:16 ` Dominik Vogt
2 siblings, 0 replies; 6+ messages in thread
From: Alan Lawrence @ 2014-11-11 15:01 UTC (permalink / raw)
To: Anthony Green; +Cc: libffi-discuss, Richard Henderson
In the meantime I believe non-iOS AArch64 builds are still broken, too?
Fix posted independently by myself and Richard Henderson:
https://sourceware.org/ml/libffi-discuss/2014/msg00134.html
https://sourceware.org/ml/libffi-discuss/2014/msg00091.html
Cheers, Alan
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.
>
> These changes will break msvc builds as well as iOS/OSX.
>
> As long as we're breaking things, I'd like to use this opportunity to
> change the header files so we have a shared set of .h files in
> /usr/include.
>
> Once things settle down from these changes, I'm hoping somebody can help
> with the msvc and iOS/OSX ports.
>
> In preparation for all of these changes, I've made a quick 3.2 release.
> There were a few nice fixes that were sitting around in the tree, and
> I'm not sure how long this next round of hacking will take.
>
> The 3.2 release should be in pretty good shape *except* for the win32/64
> msvc builds which are known to be broken. See
> https://github.com/atgreen/libffi/issues/138 for details.
>
> Thanks,
>
> AG
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libffi 3.2 and disruptive changes
2014-11-11 14:53 libffi 3.2 and disruptive changes Anthony Green
2014-11-11 14:59 ` James Greenhalgh
2014-11-11 15:01 ` Alan Lawrence
@ 2014-11-12 7:16 ` Dominik Vogt
2014-11-12 7:22 ` Richard Henderson
2 siblings, 1 reply; 6+ messages in thread
From: Dominik Vogt @ 2014-11-12 7:16 UTC (permalink / raw)
To: libffi-discuss
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.
> msvc builds which are known to be broken. See
> https://github.com/atgreen/libffi/issues/138 for details.
I've added a lengthy comment to that message report refering to
complex support and __STDC_NO_COMPLEX__. That issue needs to be
resolved.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libffi 3.2 and disruptive changes
2014-11-12 7:16 ` Dominik Vogt
@ 2014-11-12 7:22 ` Richard Henderson
0 siblings, 0 replies; 6+ messages in thread
From: Richard Henderson @ 2014-11-12 7:22 UTC (permalink / raw)
To: libffi-discuss
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~
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-11-12 12:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-11 14:53 libffi 3.2 and disruptive changes 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 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).