From: "Sergei Trofimovich via libffi-discuss" <libffi-discuss@sourceware.org>
To: libffi-discuss@sourceware.org, Anthony Green <green@moxielogic.com>
Cc: GHC developers <ghc-devs@haskell.org>,
Moritz Angermann <moritz.angermann@gmail.com>
Subject: Time for libffi release tarball?
Date: Sun, 14 May 2017 10:30:00 -0000 [thread overview]
Message-ID: <20170514113020.0d26a0c9@sf> (raw)
[-- 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 --]
next reply other threads:[~2017-05-14 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 10:30 Sergei Trofimovich via libffi-discuss [this message]
2017-05-15 17:34 ` Matthias Klose
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=20170514113020.0d26a0c9@sf \
--to=libffi-discuss@sourceware.org \
--cc=ghc-devs@haskell.org \
--cc=green@moxielogic.com \
--cc=moritz.angermann@gmail.com \
--cc=slyfox@inbox.ru \
/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).