From: "Michael S. Zick" <lkml@morethan.org>
To: linux-kernel@vger.kernel.org
Subject: Disable generation of sse3 instructions in kernel build.
Date: Sat, 9 May 2009 19:03:22 -0500 [thread overview]
Message-ID: <200905091903.25745.lkml@morethan.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Ref: 2.6.30-rcX
The option to disable sse3 instructions needs to be added to build system for x86.
Otherwise strange and mysterious things happen (tm).
Like (also attached):
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 8c86b72..3c0df6f 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -103,7 +103,7 @@ KBUILD_CFLAGS += -Wno-sign-compare
#
KBUILD_CFLAGS += -fno-asynchronous-unwind-tables
# prevent gcc from generating any FP code by mistake
-KBUILD_CFLAGS += $(call cc-option,-mno-sse -mno-mmx -mno-sse2 -mno-3dnow,)
+KBUILD_CFLAGS += $(call cc-option,-mno-sse -mno-mmx -mno-sse2 -mno-sse3 -mno-3dnow,)
KBUILD_CFLAGS += $(mflags-y)
KBUILD_AFLAGS += $(mflags-y)
[-- Attachment #2: 00-fix-kbuild-flags.patch --]
[-- Type: text/x-diff, Size: 515 bytes --]
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 8c86b72..3c0df6f 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -103,7 +103,7 @@ KBUILD_CFLAGS += -Wno-sign-compare
#
KBUILD_CFLAGS += -fno-asynchronous-unwind-tables
# prevent gcc from generating any FP code by mistake
-KBUILD_CFLAGS += $(call cc-option,-mno-sse -mno-mmx -mno-sse2 -mno-3dnow,)
+KBUILD_CFLAGS += $(call cc-option,-mno-sse -mno-mmx -mno-sse2 -mno-sse3 -mno-3dnow,)
KBUILD_CFLAGS += $(mflags-y)
KBUILD_AFLAGS += $(mflags-y)
next reply other threads:[~2009-05-10 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 0:03 Michael S. Zick [this message]
2009-05-11 21:16 ` Disable generation of sse3 instructions in kernel build Andi Kleen
[not found] ` <200905111847.46187.lkml@morethan.org>
2009-05-12 6:51 ` Andi Kleen
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=200905091903.25745.lkml@morethan.org \
--to=lkml@morethan.org \
--cc=linux-kernel@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