From: George Dunlap <george.dunlap@eu.citrix.com>
To: Tim Deegan <tim@xen.org>, xen-devel@lists.xenproject.org
Cc: keir@xen.org, ian.campbell@citrix.com, julien.grall@linaro.org,
Ian.Jackson@eu.citrix.com, george.dunlap@citrix.com,
roger.pau@citrix.com
Subject: Re: [PATCH] xen: Don't use __builtin_stdarg_start().
Date: Thu, 13 Feb 2014 15:22:13 +0000 [thread overview]
Message-ID: <52FCE325.9030008@eu.citrix.com> (raw)
In-Reply-To: <20140213151911.GD82703@deinos.phlegethon.org>
On 02/13/2014 03:19 PM, Tim Deegan wrote:
> Cset fca49a00 ("netbsd: build fix with gcc 4.5") changed the
> definition of va_start() to use __builtin_va_start() rather than
> __builtin_stdarg_start() for GCCs >= 4.5, but in fact GCC dropped
> __builtin_stdarg_start() before v3.3.
>
> Signed-off-by: Tim Deegan <tim@xen.org>
>
> ---
>
> George: this should fix the build issues Roger was having with GCC 4.5
> after my last stdarg patch.
Once it has Roger's tested-by:
Release-acked-by: George Dunlap <george.dunlap@eu.citrix.com>
next prev parent reply other threads:[~2014-02-13 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 23:29 [PATCH] xen: Don't use -nostdinc flags with CLANG Julien Grall
2014-02-11 8:37 ` Jan Beulich
2014-02-11 8:53 ` Tim Deegan
2014-02-11 12:30 ` Julien Grall
2014-02-11 12:35 ` Tim Deegan
2014-02-11 12:36 ` Julien Grall
2014-02-11 12:59 ` Tim Deegan
2014-02-11 13:20 ` Julien Grall
2014-02-11 13:59 ` Tim Deegan
2014-02-11 14:24 ` Julien Grall
2014-02-11 14:33 ` Tim Deegan
2014-02-11 15:01 ` Keir Fraser
2014-02-13 11:24 ` Tim Deegan
2014-02-13 11:46 ` George Dunlap
2014-02-13 11:49 ` George Dunlap
2014-02-13 15:19 ` [PATCH] xen: Don't use __builtin_stdarg_start() Tim Deegan
2014-02-13 15:22 ` George Dunlap [this message]
2014-02-13 15:32 ` Roger Pau Monné
2014-02-11 13:21 ` [PATCH] xen: Don't use -nostdinc flags with CLANG Julien Grall
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=52FCE325.9030008@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=keir@xen.org \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.