On Sep 1, 2008, at 9:23 AM, Sebastian Siewior wrote:
From: Thiemo Seufer <[EMAIL PROTECTED]>
those two are requried on my fresh gcc 4.3.1
Signed-off-by: Thiemo Seufer <[EMAIL PROTECTED]>
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
Not sure if this is intendent or a gcc bug but with -mno-spe
the spe opcodes were not used floating point anymore but
for 64bit save/restore for instance.
what code is getting generated for you that is causing issue?
arch/powerpc/Makefile | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
index b7d4c4c..3727e4f 100644
--- a/arch/powerpc/Makefile
+++ b/arch/powerpc/Makefile
@@ -108,7 +108,10 @@ endif
KBUILD_CFLAGS += $(call cc-option,-mno-altivec)
# No SPE instruction when building kernel
+# (We use all available options to help semi-broken compilers)
KBUILD_CFLAGS += $(call cc-option,-mno-spe)
+KBUILD_CFLAGS += $(call cc-option,-mspe=no)
Why does -mno-spe work?
From my gcc-4.3 info pages:
`-mspe=YES/NO'
This option has been deprecated. Use `-mspe' and `-mno-spe'
instead.
+KBUILD_CFLAGS += $(call cc-option,-mabi=no-spe)
is the -mabi=no-spe really needed?
- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
