From: Andrew Haley <aph@redhat.com>
To: Ian Lance Taylor <iant@golang.org>, Anthony Green <green@moxielogic.com>
Cc: Matthias Klose <doko@ubuntu.com>,
gcc Development <gcc@gcc.gnu.org>,
"libffi-discuss@sourceware.org"
<libffi-discuss@sourceware.org>
Subject: Re: libffi maintenance within GCC?
Date: Fri, 28 Oct 2016 08:17:00 -0000 [thread overview]
Message-ID: <bc656284-1027-c68e-2656-6195fccca14c@redhat.com> (raw)
In-Reply-To: <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 <green@moxielogic.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
> duplication.]
>
> 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.
Andrew.
next prev parent reply other threads:[~2016-10-28 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 12:56 Matthias Klose
2016-10-27 13:09 ` Anthony Green
2016-10-28 3:03 ` Ian Lance Taylor
2016-10-28 8:17 ` Andrew Haley [this message]
2016-10-27 13:59 ` Andrew Haley
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=bc656284-1027-c68e-2656-6195fccca14c@redhat.com \
--to=aph@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=iant@golang.org \
--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).