public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] powerpc/85xx: select -mcpu=8540 to match -Wa, e500
Date: Fri, 18 Jan 2013 19:38:16 -0600	[thread overview]
Message-ID: <20130119013816.GA10517@buserror.net> (raw)
In-Reply-To: <20130109014318.GA31134@buserror.net>

This allows building with toolchains that by default target e6500.

When targetting e6500, GCC generates a two-operand form of mfcr which gas
normally maps to mfocr.  However, when we tell gas to target e500 rather
than e6500, it rejects two-operand mfcr.  Tell GCC to target a
least-common-denominator e500 to match what we tell the assembler.

-misel and -mno-strict-align are added to keep the code size from growing
(it actually ends up shrinking a bit compared to -mcpu=603e, which was
the default on my old toolchain).

Signed-off-by: Scott Wood <scottwood@freescale.com>
---
v2: add -misel and -mno-strict-align

 arch/powerpc/cpu/mpc85xx/config.mk |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/powerpc/cpu/mpc85xx/config.mk b/arch/powerpc/cpu/mpc85xx/config.mk
index f36d823..450d511 100644
--- a/arch/powerpc/cpu/mpc85xx/config.mk
+++ b/arch/powerpc/cpu/mpc85xx/config.mk
@@ -23,7 +23,8 @@
 
 PLATFORM_RELFLAGS += -meabi
 
-PLATFORM_CPPFLAGS += -ffixed-r2 -Wa,-me500 -msoft-float -mno-string
+PLATFORM_CPPFLAGS += -ffixed-r2 -mcpu=8540 -misel -mno-strict-align \
+	-Wa,-me500 -msoft-float -mno-string
 
 # -mspe=yes is needed to have -mno-spe accepted by a buggy GCC;
 # see "[PATCH,rs6000] make -mno-spe work as expected" on
-- 
1.7.9.5

  reply	other threads:[~2013-01-19  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09  1:43 [U-Boot] [PATCH] powerpc/85xx: select -mcpu=8540 to match -Wa, e500 Scott Wood
2013-01-19  1:38 ` Scott Wood [this message]
2013-01-24  8:07   ` [U-Boot] [PATCH v2] " Andy Fleming
2013-01-25  0:21     ` Scott Wood

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=20130119013816.GA10517@buserror.net \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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