This is the mail archive of the
mailing list for the GCC project.
Re: libffi maintenance within GCC?
- From: Andrew Haley <aph at redhat dot com>
- To: Ian Lance Taylor <iant at golang dot org>, 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: Fri, 28 Oct 2016 09:17:36 +0100
- Subject: Re: libffi maintenance within GCC?
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <CACxje5-WNcJnWkfK4QyOf0=gsDySxmJ6vU=HnxdjMertyDjMfA@mail.gmail.com> <CAKOQZ8wU02wBiP3K6ekW73SgDFCxQzBJ_0GggnypZn9bJ1ZXbA@mail.gmail.com>
On 28/10/16 04:03, Ian Lance Taylor wrote:
> On Thu, Oct 27, 2016 at 6:08 AM, Anthony Green <email@example.com> 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.
It has been very convenient for GCC port maintainers to be able to
commit their patches to the GCC tree.