From: Richard Henderson <rth@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: [PATCH 0/7] Merge of gcc patches
Date: Tue, 18 Nov 2014 10:32:00 -0000 [thread overview]
Message-ID: <546B201A.1070703@redhat.com> (raw)
In-Reply-To: <20141118101743.GA26714@linux.vnet.ibm.com>
On 11/18/2014 11:17 AM, Dominik Vogt wrote:
> The following series of patches merges the changes in gcc's copy
> of libffi since this gcc-commit:
>
> 2012-12-26 16:28 green * <libffi-last-merge> libffi merge
>
> While I've tried to resolve conflicts in a sensible way, I've not
> made any effort to check what the patches do or whether they are
> (still) useful, so please double check before checking in. libffi
> still compiles after applying the patches 1 to 7 (without path
> "0", see below), but I've not run any tests.
>
> The "zeroth" patch is attached right to this message. To me it
> looks like a patch that is applied to gcc every time libffi is
> merged, but there may be unrelated bits; I cannot judge that. (The
> patch conflicts with a later patch in the series, but the conflict
> is easy to resolve.)
I wonder how much of this we could merge with an
AM_CONDITIONAL(IN_GCC, ...)
where the setting of IN_GCC of course changes between the standalone and
in-tree builds.
r~
next prev parent reply other threads:[~2014-11-18 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 10:17 Dominik Vogt
2014-11-18 10:18 ` [PATCH 2/7] " Dominik Vogt
2014-11-18 10:34 ` Richard Henderson
2014-11-18 10:18 ` [PATCH 1/7] " Dominik Vogt
2014-11-18 10:33 ` Richard Henderson
2014-11-18 13:13 ` Richard Henderson
2014-11-18 10:19 ` [PATCH 3/7] " Dominik Vogt
2014-11-18 10:40 ` Richard Henderson
2014-11-18 10:19 ` [PATCH 4/7] " Dominik Vogt
2014-11-18 10:41 ` Richard Henderson
2014-11-18 10:20 ` [PATCH 6/7] " Dominik Vogt
2014-11-18 10:36 ` Richard Henderson
2014-11-18 11:06 ` Dominik Vogt
2014-11-18 11:34 ` Richard Henderson
2014-11-18 11:57 ` Dominik Vogt
2014-11-18 10:20 ` [PATCH 5/7] " Dominik Vogt
2014-11-18 10:42 ` Richard Henderson
2014-11-18 10:21 ` [PATCH 7/7] " Dominik Vogt
2014-11-18 10:37 ` Richard Henderson
2014-11-18 10:32 ` Richard Henderson [this message]
2014-11-18 10:47 ` [PATCH 0/7] " Richard Henderson
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=546B201A.1070703@redhat.com \
--to=rth@redhat.com \
--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).