This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Time for libffi release tarball?

From: "Sergei Trofimovich via libffi-discuss" <libffi-discuss at sourceware dot org>
To: libffi-discuss at sourceware dot org, Anthony Green <green at moxielogic dot com>
Cc: GHC developers <ghc-devs at haskell dot org>, Moritz Angermann <moritz dot angermann at gmail dot com>
Date: Sun, 14 May 2017 11:30:20 +0100
Subject: Time for libffi release tarball?
Authentication-results: sourceware.org; auth=none
Authentication-results: smtp18.mail.ru; auth=pass smtp.auth=slyfox at inbox dot ru smtp.mailfrom=slyfox at inbox dot ru
Reply-to: Sergei Trofimovich <slyfox at inbox dot ru>

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: pgpcztQ_qWYUE.pgp
Description: Цифровая подпись OpenPGP

Follow-Ups:
- Re: Time for libffi release tarball?
  - From: Matthias Klose

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]