From: Jeff Garzik <jgarzik@pobox.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: arjanv@redhat.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: [BK/PATCH] better i386 compiler flags
Date: Fri, 10 Jan 2003 20:26:46 -0500 [thread overview]
Message-ID: <20030111012645.GB24847@gtf.org> (raw)
[this kills scads of warnings with CONFIG_MCYRIXIII and gcc 3.2,
also starts using -march=pentium3/4/athlon when available. I've been
doing that for a while now without problems.]
Marcelo, please do a
bk pull bk://kernel.bkbits.net/jgarzik/misc-2.4
This will update the following files:
arch/i386/Makefile | 19 +++++++++++--------
1 files changed, 11 insertions(+), 8 deletions(-)
through these ChangeSets:
<jgarzik@redhat.com> (03/01/10 1.994)
arch/i386/Makefile: improved support for gcc 3.2 compiler flags
* Adds useful 'check_gcc' makefile function
* stop using the deprecated -malign* arguments when -falign* is available
* call -march={pentium3,pentium4,k6,athlon,c3,winchip*} when available
--- 1.4/arch/i386/Makefile Mon Sep 30 12:45:01 2002
+++ edited/arch/i386/Makefile Fri Jan 10 19:49:03 2003
@@ -23,8 +23,10 @@
CFLAGS += -pipe
+check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
+
# prevent gcc from keeping the stack 16 byte aligned
-CFLAGS += $(shell if $(CC) -mpreferred-stack-boundary=2 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-mpreferred-stack-boundary=2"; fi)
+CFLAGS += $(call check_gcc,-mpreferred-stack-boundary=2,)
ifdef CONFIG_M386
CFLAGS += -march=i386
@@ -51,19 +53,19 @@
endif
ifdef CONFIG_MPENTIUMIII
-CFLAGS += -march=i686
+CFLAGS += $(call check_gcc,-march=pentium3,-march=i686)
endif
ifdef CONFIG_MPENTIUM4
-CFLAGS += -march=i686
+CFLAGS += $(call check_gcc,-march=pentium4,-march=i686)
endif
ifdef CONFIG_MK6
-CFLAGS += $(shell if $(CC) -march=k6 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-march=k6"; else echo "-march=i586"; fi)
+CFLAGS += $(call check_gcc,-march=k6,-march=i586)
endif
ifdef CONFIG_MK7
-CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686 -malign-functions=4"; fi)
+CFLAGS += $(call check_gcc,-march=athlon,-march=i686 -malign-functions=4)
endif
ifdef CONFIG_MCRUSOE
@@ -71,11 +73,11 @@
endif
ifdef CONFIG_MWINCHIPC6
-CFLAGS += -march=i586
+CFLAGS += $(call check_gcc,-march=winchip-c6,-march=i586)
endif
ifdef CONFIG_MWINCHIP2
-CFLAGS += -march=i586
+CFLAGS += $(call check_gcc,-march=winchip2,-march=i586)
endif
ifdef CONFIG_MWINCHIP3D
@@ -83,7 +85,8 @@
endif
ifdef CONFIG_MCYRIXIII
-CFLAGS += -march=i486 -malign-functions=0 -malign-jumps=0 -malign-loops=0
+CFLAGS += $(call check_gcc,-march=c3,-march=i486)
+CFLAGS += $(call check_gcc,-falign-functions=0 -falign-jumps=0 -falign-loops=0,-malign-functions=0 -malign-jumps=0 -malign-loops=0)
endif
HEAD := arch/i386/kernel/head.o arch/i386/kernel/init_task.o
next reply other threads:[~2003-01-11 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 1:26 Jeff Garzik [this message]
2003-01-12 0:06 ` [BK/PATCH] better i386 compiler flags Dave Jones
2003-01-12 7:29 ` Richard Henderson
2003-01-12 14:52 ` Dave Jones
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=20030111012645.GB24847@gtf.org \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.