* Re: Unreviewed libffi patch
[not found] <yddk3mrtk3k.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
@ 2013-05-22 9:58 ` Andrew Haley
[not found] ` <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Haley @ 2013-05-22 9:58 UTC (permalink / raw)
To: libffi-discuss; +Cc: Rainer Orth
On 05/22/2013 10:55 AM, Rainer Orth wrote:
> The following libffi patch
>
> [libffi] Fix several libffi testsuite failures on 64-bit SPARC and PowerPC (PR libffi/56033)
> http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00840.html
>
> has remained unreviewed for a week. It needs a libffi maintainer, which
> I suppose Anthony still is, despite not being listed in MAINTAINERS.
Forwarding to libffi.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unreviewed libffi patch
[not found] ` <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com>
@ 2013-05-22 11:49 ` Rainer Orth
2013-05-22 12:40 ` Jakub Jelinek
0 siblings, 1 reply; 6+ messages in thread
From: Rainer Orth @ 2013-05-22 11:49 UTC (permalink / raw)
To: Anthony Green; +Cc: Andrew Haley, libffi-discuss, gcc-patches, Jakub Jelinek
Anthony Green <green@moxielogic.com> writes:
> Rainer - sorry, I've been travelling and falling behind on email.
> This patch is fine. Please commit it to GCC. I'll put it in the
> libffi git tree.
No worries, I just saw your vacation note. I've commited to mainline
now.
Jakub, what should we do about the 4.8 branch? Wait until 4.8.1 is
released or apply now? This is a regression from 4.7.
Thanks.
Rainer
> On Wed, May 22, 2013 at 5:58 AM, Andrew Haley <aph@redhat.com> wrote:
>
> On 05/22/2013 10:55 AM, Rainer Orth wrote:
> > The following libffi patch
> >
> > [libffi] Fix several libffi testsuite failures on 64-bit
> SPARC and PowerPC (PR libffi/56033)
> > http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00840.html
> >
> > has remained unreviewed for a week. It needs a libffi
> maintainer, which
> > I suppose Anthony still is, despite not being listed in
> MAINTAINERS.
>
> Forwarding to libffi.
>
>
>
>
>
>
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unreviewed libffi patch
2013-05-22 11:49 ` Rainer Orth
@ 2013-05-22 12:40 ` Jakub Jelinek
2013-05-22 12:45 ` Rainer Orth
0 siblings, 1 reply; 6+ messages in thread
From: Jakub Jelinek @ 2013-05-22 12:40 UTC (permalink / raw)
To: Rainer Orth; +Cc: Anthony Green, Andrew Haley, libffi-discuss, gcc-patches
On Wed, May 22, 2013 at 01:49:47PM +0200, Rainer Orth wrote:
> Jakub, what should we do about the 4.8 branch? Wait until 4.8.1 is
> released or apply now? This is a regression from 4.7.
You can apply it now.
Jakub
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unreviewed libffi patch
2013-05-22 12:40 ` Jakub Jelinek
@ 2013-05-22 12:45 ` Rainer Orth
0 siblings, 0 replies; 6+ messages in thread
From: Rainer Orth @ 2013-05-22 12:45 UTC (permalink / raw)
To: Jakub Jelinek; +Cc: Anthony Green, Andrew Haley, libffi-discuss, gcc-patches
Jakub Jelinek <jakub@redhat.com> writes:
> On Wed, May 22, 2013 at 01:49:47PM +0200, Rainer Orth wrote:
>> Jakub, what should we do about the 4.8 branch? Wait until 4.8.1 is
>> released or apply now? This is a regression from 4.7.
>
> You can apply it now.
Done, thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unreviewed libffi patch
2011-06-14 15:38 ` Andrew Haley
@ 2011-06-14 16:02 ` Rainer Orth
0 siblings, 0 replies; 6+ messages in thread
From: Rainer Orth @ 2011-06-14 16:02 UTC (permalink / raw)
To: Andrew Haley; +Cc: gcc-patches, libffi-discuss
Andrew Haley <aph@redhat.com> writes:
> On 06/14/2011 04:22 PM, Rainer Orth wrote:
>> The following patch has remained unreviewed for a week:
>
> I think it wasn't cc'd to libffi-discuss@sourceware.org
Right, I hadn't known/had forgotten about that since all my libffi fixes
happen in GCC context. I'd only Cc'ed it to Anthony, but he isn't
listed as libffi maintainer in MAINTAINERS anymore as I just noticed.
>> [libffi] Fix libffi.call/huge_struct.c on Tru64 UNIX
>> http://gcc.gnu.org/ml/gcc-patches/2011-06/msg00644.html
>>
>> It needs a libffi maintainer or global reviewer.
>
> This is OK.
Installed, thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Unreviewed libffi patch
[not found] <yddpqmg5tgk.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
@ 2011-06-14 15:38 ` Andrew Haley
2011-06-14 16:02 ` Rainer Orth
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Haley @ 2011-06-14 15:38 UTC (permalink / raw)
To: gcc-patches; +Cc: libffi-discuss
On 06/14/2011 04:22 PM, Rainer Orth wrote:
> The following patch has remained unreviewed for a week:
I think it wasn't cc'd to libffi-discuss@sourceware.org
> [libffi] Fix libffi.call/huge_struct.c on Tru64 UNIX
> http://gcc.gnu.org/ml/gcc-patches/2011-06/msg00644.html
>
> It needs a libffi maintainer or global reviewer.
This is OK.
Andrew.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-05-22 12:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <yddk3mrtk3k.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
2013-05-22 9:58 ` Unreviewed libffi patch Andrew Haley
[not found] ` <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com>
2013-05-22 11:49 ` Rainer Orth
2013-05-22 12:40 ` Jakub Jelinek
2013-05-22 12:45 ` Rainer Orth
[not found] <yddpqmg5tgk.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
2011-06-14 15:38 ` Andrew Haley
2011-06-14 16:02 ` Rainer Orth
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).