This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: libffi maintenance
- From: Andrew Haley <aph at redhat dot com>
- To: Anthony Green <green at moxielogic dot com>, "libffi-discuss at sourceware dot org" <libffi-discuss at sourceware dot org>
- Date: Tue, 3 May 2016 08:41:31 +0100
- Subject: Re: libffi maintenance
- Authentication-results: sourceware.org; auth=none
- References: <CACxje5_N-oPFqCyX-JpOK+W1MwnP98p9ixh+HJyDG=HdaTqnrA at mail dot gmail dot 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.