This is the mail archive of the
mailing list for the GCC project.
Re: libffi maintenance within GCC?
- From: Ian Lance Taylor <iant at golang dot org>
- To: Anthony Green <green at moxielogic dot com>
- Cc: Matthias Klose <doko at ubuntu dot com>, gcc Development <gcc at gcc dot gnu dot org>, "libffi-discuss at sourceware dot org" <libffi-discuss at sourceware dot org>
- Date: Thu, 27 Oct 2016 20:03:00 -0700
- Subject: Re: libffi maintenance within GCC?
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <CACxje5-WNcJnWkfK4QyOf0=gsDySxmJ6vU=HnxdjMertyDjMfA@mail.gmail.com>
On Thu, Oct 27, 2016 at 6:08 AM, Anthony Green <firstname.lastname@example.org> wrote:
> Is it still important that libffi be included in the GCC tree?
[ Replying again as last message was bounced as HTML--sorry for the
libffi is used by libgo, for much the same reason as it was used by
libjava, so it needs to come from somewhere.
> On Thu, Oct 27, 2016 at 8:55 AM, Matthias Klose <email@example.com> wrote:
>> With the removal of libgcj, the only user of libffi in GCC is libgo, however
>> there is now no maintainer listed anymore for libffi in the MAINTAINERS file,
>> and the libffi subdir is a bit outdated compared to the libffi upstream
>> repository (got aware of this by libffi issue #197). Who would be responsible
>> now to update / review libffi patches, just the global reviewers, or should
>> libffi be maintained by the libgo maintainers?