From: Andrew Haley <aph@redhat.com>
To: Anthony Green <green@moxielogic.com>,
"libffi-discuss@sourceware.org"
<libffi-discuss@sourceware.org>
Subject: Re: libffi maintenance
Date: Tue, 03 May 2016 07:41:00 -0000 [thread overview]
Message-ID: <5728562B.2070408@redhat.com> (raw)
In-Reply-To: <CACxje5_N-oPFqCyX-JpOK+W1MwnP98p9ixh+HJyDG=HdaTqnrA@mail.gmail.com>
On 02/05/16 14:51, Anthony Green wrote:
> In addition, I've granted write permission to three trusted and active
> hackers: Tom Tromey, Richard Henderson and Josh Triplett. I plan on
> spending a little more time on libffi soon, but there's been a log jam
> of PRs over the past year, and I hope this change will help move
> things along.
We should have the conversation about what to do about the old and
stale libffi in the GCC tree. It's caused me (and probably plenty of
others) a great deal of confusion this year, with various bug fixes
and improvements to merge one way or the other. In particular, I
still don't really know where development happens: some of it happens
in GCC and some in libffi upstream.
I'd like libffi to be gone from the GCC repo, but that's probably not
possible. I intend to delete libgcj, but I think that gccgo still
uses libffi.
Andrew.
next prev parent reply other threads:[~2016-05-03 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 13:51 Anthony Green
2016-05-03 7:41 ` Andrew Haley [this message]
2016-05-03 7:50 ` Jakub Jelinek
2016-05-03 14:39 ` Richard Henderson
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=5728562B.2070408@redhat.com \
--to=aph@redhat.com \
--cc=green@moxielogic.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).