* libffi maintenance within GCC?
@ 2016-10-27 12:56 Matthias Klose
2016-10-27 13:09 ` Anthony Green
2016-10-27 13:59 ` Andrew Haley
0 siblings, 2 replies; 5+ messages in thread
From: Matthias Klose @ 2016-10-27 12:56 UTC (permalink / raw)
To: gcc Development; +Cc: libffi-discuss, Ian Lance Taylor
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?
Matthias
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libffi maintenance within GCC?
2016-10-27 12:56 libffi maintenance within GCC? Matthias Klose
@ 2016-10-27 13:09 ` Anthony Green
2016-10-28 3:03 ` Ian Lance Taylor
2016-10-27 13:59 ` Andrew Haley
1 sibling, 1 reply; 5+ messages in thread
From: Anthony Green @ 2016-10-27 13:09 UTC (permalink / raw)
To: Matthias Klose; +Cc: gcc Development, libffi-discuss, Ian Lance Taylor
Is it still important that libffi be included in the GCC tree?
AG
On Thu, Oct 27, 2016 at 8:55 AM, Matthias Klose <doko@ubuntu.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?
>
> Matthias
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libffi maintenance within GCC?
2016-10-27 12:56 libffi maintenance within GCC? Matthias Klose
2016-10-27 13:09 ` Anthony Green
@ 2016-10-27 13:59 ` Andrew Haley
1 sibling, 0 replies; 5+ messages in thread
From: Andrew Haley @ 2016-10-27 13:59 UTC (permalink / raw)
To: Matthias Klose, gcc Development, Anthony Green
Cc: libffi-discuss, Ian Lance Taylor
On 27/10/16 13:55, Matthias Klose 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?
libffi has always been maintained by the appropriate back-end maintainers.
Andrew.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libffi maintenance within GCC?
2016-10-27 13:09 ` Anthony Green
@ 2016-10-28 3:03 ` Ian Lance Taylor
2016-10-28 8:17 ` Andrew Haley
0 siblings, 1 reply; 5+ messages in thread
From: Ian Lance Taylor @ 2016-10-28 3:03 UTC (permalink / raw)
To: Anthony Green; +Cc: Matthias Klose, gcc Development, libffi-discuss
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.
Ian
> On Thu, Oct 27, 2016 at 8:55 AM, Matthias Klose <doko@ubuntu.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?
>>
>> Matthias
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libffi maintenance within GCC?
2016-10-28 3:03 ` Ian Lance Taylor
@ 2016-10-28 8:17 ` Andrew Haley
0 siblings, 0 replies; 5+ messages in thread
From: Andrew Haley @ 2016-10-28 8:17 UTC (permalink / raw)
To: Ian Lance Taylor, Anthony Green
Cc: Matthias Klose, gcc Development, libffi-discuss
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-10-28 8:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-27 12:56 libffi maintenance within GCC? Matthias Klose
2016-10-27 13:09 ` Anthony Green
2016-10-28 3:03 ` Ian Lance Taylor
2016-10-28 8:17 ` Andrew Haley
2016-10-27 13:59 ` Andrew Haley
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).