From: Jonathan Bastien-Filiatrault <Intuxicated_kdev@yahoo.ca>
To: mec@shout.net
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.5.69 Change to i386 Makefile to distinguish athlons.
Date: Wed, 14 May 2003 14:57:21 -0400 [thread overview]
Message-ID: <3EC29191.5030700@yahoo.ca> (raw)
It should succesfully set -march=athlon-<type> according to uname -p.
--- linux-2.5.69/arch/i386/Makefile.orig 2003-05-14
13:37:19.000000000 -0400
+++ linux-2.5.69/arch/i386/Makefile 2003-05-14 14:50:03.000000000 -0400
@@ -23,7 +23,7 @@
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)
-
+get_athlon_type = ${shell case `uname -p` in "* 4 *") echo
"athlon-4";;*XP*) echo "athlon-xp";;*MP*) echo "athlon-mp";;*) echo
"athlon";;esac}
# prevent gcc from keeping the stack 16 byte aligned
CFLAGS += $(call check_gcc,-mpreferred-stack-boundary=2,)
@@ -39,7 +39,7 @@
cflags-$(CONFIG_MPENTIUMIII) += $(call
check_gcc,-march=pentium3,-march=i686)
cflags-$(CONFIG_MPENTIUM4) += $(call
check_gcc,-march=pentium4,-march=i686)
cflags-$(CONFIG_MK6) += $(call check_gcc,-march=k6,-march=i586)
-cflags-$(CONFIG_MK7) += $(call
check_gcc,-march=athlon,-march=i686 $(align)-functions=4)
+cflags-$(CONFIG_MK7) += $(call check_gcc,-march=$(call
get_athlon_type),-march=i686 $(align)-functions=4)
cflags-$(CONFIG_MK8) += $(call check_gcc,-march=k8,$(call
check_gcc,-march=athlon,-march=i686 $(align)-functions=4))
cflags-$(CONFIG_MCRUSOE) += -march=i686 $(align)-functions=0
$(align)-jumps=0 $(align)-loops=0
cflags-$(CONFIG_MWINCHIPC6) += $(call
check_gcc,-march=winchip-c6,-march=i586)
next reply other threads:[~2003-05-14 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 18:57 Jonathan Bastien-Filiatrault [this message]
2003-05-14 20:03 ` [PATCH] 2.5.69 Change to i386 Makefile to distinguish athlons Dave Jones
2003-05-14 20:47 ` Sam Ravnborg
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=3EC29191.5030700@yahoo.ca \
--to=intuxicated_kdev@yahoo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
/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