From: Sam Ravnborg <sam@ravnborg.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@saturn.ravnborg.org>,
Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@suse.de>
Subject: [PATCH 2/5] x86: share more options between 32 and 64 bit build
Date: Sat, 29 Dec 2007 21:41:13 +0100 [thread overview]
Message-ID: <1198960876-21159-2-git-send-email-sam@ravnborg.org> (raw)
In-Reply-To: <1198960876-21159-1-git-send-email-sam@ravnborg.org>
From: Sam Ravnborg <sam@saturn.ravnborg.org>
On recommendation from Andi Kleen share a few more options
between 32 and 64 bit builds.
A defconfig build for i386 did not show any difference in
size of text and data.
The additional shared options are:
-Wno-sign-compare
-fno-asynchronous-unwind-tables
-mno-sse
-mno-mmx
-mno-sse2
-mno-3dnow
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <ak@suse.de>
---
arch/x86/Makefile | 12 ++++++++----
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index e5fbad6..4124df5 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -64,14 +64,10 @@ else
KBUILD_CFLAGS += -mno-red-zone
KBUILD_CFLAGS += -mcmodel=kernel
- KBUILD_CFLAGS += -Wno-sign-compare
- KBUILD_CFLAGS += -fno-asynchronous-unwind-tables
# -funit-at-a-time shrinks the kernel .text considerably
# unfortunately it makes reading oopses harder.
KBUILD_CFLAGS += $(call cc-option,-funit-at-a-time)
- # prevent gcc from generating any FP code by mistake
- KBUILD_CFLAGS += $(call cc-option,-mno-sse -mno-mmx -mno-sse2 -mno-3dnow,)
# this works around some issues with generating unwind tables in older gccs
# newer gccs do it by default
KBUILD_CFLAGS += -maccumulate-outgoing-args
@@ -98,7 +94,15 @@ KBUILD_CFLAGS += $(cfi) $(cfi-sigframe)
LDFLAGS := -m elf_$(UTS_MACHINE)
OBJCOPYFLAGS := -O binary -R .note -R .comment -S
+
+# Speed up the build
KBUILD_CFLAGS += -pipe
+# Workaround for a gcc prelease that unfortunately was shipped in a suse release
+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,)
###
# Sub architecture support
--
1.5.3.7.1112.g9758e
next prev parent reply other threads:[~2007-12-29 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 20:38 [PATCH 0/5] x86 makefile unification and cleaning Sam Ravnborg
2007-12-29 20:41 ` [PATCH 1/5] x86: unification of arch/x86/Makefiles Sam Ravnborg
2007-12-29 20:41 ` Sam Ravnborg [this message]
2007-12-29 20:41 ` [PATCH 3/5] x86: biarch support for 32 bit builds beautified Sam Ravnborg
2007-12-29 20:41 ` [PATCH 4/5] x86: teach vdso to clean Sam Ravnborg
2007-12-29 20:41 ` [PATCH 5/5] " Sam Ravnborg
2007-12-29 20:44 ` [PATCH 0/5] x86 makefile unification and cleaning Sam Ravnborg
2007-12-30 14:45 ` Ingo Molnar
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=1198960876-21159-2-git-send-email-sam@ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@saturn.ravnborg.org \
--cc=tglx@linutronix.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