public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: gcc-patches@gcc.gnu.org, Mike Stump <mikestump@comcast.net>,
	Chung-Lin Tang <cltang@codesourcery.com>,
	Ian Lance Taylor <iant@golang.org>,
	 libffi-discuss@sourceware.org
Subject: Re: [PATCH v5 GCC] libffi/test: Fix compilation for build sysroot
Date: Wed, 29 Apr 2020 11:14:35 -0600	[thread overview]
Message-ID: <10b639b335a1f9a064a40410f79fe4c0ba9b749e.camel@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2004252128560.15294@redsun52.ssa.fujisawa.hgst.com>

On Sat, 2020-04-25 at 21:33 +0100, Maciej W. Rozycki wrote:
> On Wed, 22 Apr 2020, Jeff Law wrote:
> 
> > > 	libffi/
> > > 	* Makefile.am (DISTCLEANFILES): New variable.
> > > 	* configure.ac: Produce `local.exp'.
> > > 	* Makefile.in: Regenerate.
> > > 	* configure: Regenerate.
> > > 	* testsuite/Makefile.am (EXTRA_DEJAGNU_SITE_CONFIG): New 
> > > 	variable.
> > > 	* testsuite/Makefile.in: Regenerate.
> > OK
> > jeff
> 
>  Committed now then, according to schedule, thanks for your review.  We 
> may revisit the backport of improvements I previously proposed when/if the 
> upstream libffi maintainer decides to accept them.
ACK.

FWIW, I'm expecting Florian to be digging into some libffi stuff relatively soon
and once those issues are ironed out, there'll be a push for a libffi upstream
release -- which seems like a good place to re-sync GCC to the upstream libffi
master.

jeff


  reply	other threads:[~2020-04-29 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 13:18 Maciej W. Rozycki
2020-04-22 18:04 ` Jeff Law
2020-04-25 20:33   ` Maciej W. Rozycki
2020-04-29 17:14     ` Jeff Law [this message]
2020-04-29 20:48       ` Florian Weimer

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=10b639b335a1f9a064a40410f79fe4c0ba9b749e.camel@redhat.com \
    --to=law@redhat.com \
    --cc=cltang@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@golang.org \
    --cc=libffi-discuss@sourceware.org \
    --cc=macro@wdc.com \
    --cc=mikestump@comcast.net \
    /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).