From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] arm: fix build with gcc 4.7.x
Date: Tue, 3 Jul 2012 18:09:28 +0100 [thread overview]
Message-ID: <4FF32748.9060707@citrix.com> (raw)
In-Reply-To: <4FE86056020000780008BABB@nat28.tlf.novell.com>
On 25/06/12 11:57, Jan Beulich wrote:
> As was already pointed out months ago (see
> http://lists.xen.org/archives/html/xen-devel/2012-02/msg00826.html),
> gcc 4.7.x (imo validly) refuses to take both -mcpu=cortex-a15 and
> -march=armv7-a due to conflicting feature sets causing amibiguity in
> instruction selection. Since the former implies the latter, just use
> the former (and drop the -march=).
Given that we currently use the v7-A envelope model rather than a
Cortex-A15 I think -march=armv7-a is the correct option.
David
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/arm/Rules.mk
> +++ b/xen/arch/arm/Rules.mk
> @@ -24,7 +24,7 @@ ifneq ($(call cc-option,$(CC),-fvisibili
> CFLAGS += -DGCC_HAS_VISIBILITY_ATTRIBUTE
> endif
>
> -CFLAGS += -march=armv7-a -mcpu=cortex-a15 -mfpu=vfpv3 -mfloat-abi=softfp
> +CFLAGS += -mcpu=cortex-a15 -mfpu=vfpv3 -mfloat-abi=softfp
>
> # Require GCC v3.4+ (to avoid issues with alignment constraints in Xen headers)
> check-$(gcc) = $(call cc-ver-check,CC,0x030400,"Xen requires at least gcc-3.4")
next prev parent reply other threads:[~2012-07-03 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 10:57 [PATCH] arm: fix build with gcc 4.7.x Jan Beulich
2012-06-25 11:18 ` Ian Campbell
2012-07-03 17:09 ` David Vrabel [this message]
2012-07-04 6:05 ` Jan Beulich
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=4FF32748.9060707@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xensource.com \
/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.