public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
* Time for libffi release tarball?
@ 2017-05-14 10:30 Sergei Trofimovich via libffi-discuss
  2017-05-15 17:34 ` Matthias Klose
  0 siblings, 1 reply; 2+ messages in thread
From: Sergei Trofimovich via libffi-discuss @ 2017-05-14 10:30 UTC (permalink / raw)
  To: libffi-discuss, Anthony Green; +Cc: GHC developers, Moritz Angermann

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Hello libffi devs!

GHC (http://www.haskell.org/ghc/), a portable haskell compiler,
uses libffi to implement calls into and back from C.

Latest libffi-3.2.1 was released on November 12, 2014.

One of problematic targets is ARMv7 iOS (clang):

A few relevant commits:
    https://github.com/libffi/libffi/commit/bc4fc07aa58df6d7fa90b57d305d58eef96a0416
    https://github.com/libffi/libffi/commit/e3d2812ce43940aacae5bab2d0e965278cb1e7ea

What do you think of releasing libffi tarball with these fixes?

Would it make sense to cut libffi releases roughly at the same
time major gcc releases are cut?

This email is mostly the same ping from
    https://github.com/libffi/libffi/issues/296

Thank you!

-- 

  Sergei

[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Time for libffi release tarball?
  2017-05-14 10:30 Time for libffi release tarball? Sergei Trofimovich via libffi-discuss
@ 2017-05-15 17:34 ` Matthias Klose
  0 siblings, 0 replies; 2+ messages in thread
From: Matthias Klose @ 2017-05-15 17:34 UTC (permalink / raw)
  To: Sergei Trofimovich, libffi-discuss, Anthony Green
  Cc: GHC developers, Moritz Angermann

On 14.05.2017 03:30, Sergei Trofimovich via libffi-discuss wrote:
> Hello libffi devs!
> 
> GHC (http://www.haskell.org/ghc/), a portable haskell compiler,
> uses libffi to implement calls into and back from C.
> 
> Latest libffi-3.2.1 was released on November 12, 2014.
> 
> One of problematic targets is ARMv7 iOS (clang):
> 
> A few relevant commits:
>     https://github.com/libffi/libffi/commit/bc4fc07aa58df6d7fa90b57d305d58eef96a0416
>     https://github.com/libffi/libffi/commit/e3d2812ce43940aacae5bab2d0e965278cb1e7ea
> 
> What do you think of releasing libffi tarball with these fixes?
> 
> Would it make sense to cut libffi releases roughly at the same
> time major gcc releases are cut?
> 
> This email is mostly the same ping from
>     https://github.com/libffi/libffi/issues/296
> 
> Thank you!

Two days ago, I did a libffi trunk test build, see
https://buildd.debian.org/status/package.php?p=libffi&suite=experimental

found a regression building on x86_64-linux-gnux32 (see issue #306).

Yes, I think a release is really needed, but unfortunately there was no feedback
since my last question from October 2016.  There is the #libffi channel on
Freenode as well, but I didn't see agreen there either for a long time.

Matthias

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-05-15 17:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-14 10:30 Time for libffi release tarball? Sergei Trofimovich via libffi-discuss
2017-05-15 17:34 ` Matthias Klose

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).