public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@openembedded.org>
To: linux-omap@vger.kernel.org
Cc: Koen Kooi <koen@openembedded.org>
Subject: [PATCH] ARM: OMAP: armv7a Makefile: change -march flag to "armv7-a" so gcc 4.3.x works
Date: Fri, 13 Jun 2008 16:45:51 +0200	[thread overview]
Message-ID: <1213368351-10664-1-git-send-email-koen@openembedded.org> (raw)

armv7a Makefile: change -march flag to "armv7-a" so gcc 4.3.x works, "armv7a" is a CSL-ism. CSL compilers accept both variants.

Tested with: gcc 4.2.4, 4.3.0, 4.3.1 and csl 2007q3, 2008q1

Signed-off-by: Koen Kooi <koen@openembedded.org>
---
 arch/arm/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index 40a0b44..a3befbd 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -47,7 +47,7 @@ comma = ,
 # Note that GCC does not numerically define an architecture version
 # macro, but instead defines a whole series of macros which makes
 # testing for a specific architecture or later rather impossible.
-arch-$(CONFIG_CPU_32v7)		:=-D__LINUX_ARM_ARCH__=7 $(call cc-option,-march=armv7a,-march=armv5t -Wa$(comma)-march=armv7a)
+arch-$(CONFIG_CPU_32v7)		:=-D__LINUX_ARM_ARCH__=7 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
 arch-$(CONFIG_CPU_32v6)		:=-D__LINUX_ARM_ARCH__=6 $(call cc-option,-march=armv6,-march=armv5t -Wa$(comma)-march=armv6)
 # Only override the compiler option if ARMv6. The ARMv6K extensions are
 # always available in ARMv7
-- 
1.5.4.3


             reply	other threads:[~2008-06-13 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 14:45 Koen Kooi [this message]
2008-06-16 13:25 ` [PATCH] ARM: OMAP: armv7a Makefile: change -march flag to "armv7-a" so gcc 4.3.x works Tony Lindgren
2008-06-16 13:50   ` Koen Kooi

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=1213368351-10664-1-git-send-email-koen@openembedded.org \
    --to=koen@openembedded.org \
    --cc=linux-omap@vger.kernel.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