All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: CPU type .config <-> i386/Makefile question[s]
Date: Sun, 5 Jun 2005 14:58:50 +0100	[thread overview]
Message-ID: <200506051458.50307.nick@linicks.net> (raw)

Hello all,

I am still a n00b here learning, so by all means tell me to get lost if what I 
am about to say is total bollocks...

I was just running through building the new 2.4.31 kernel on my Quake2 box, 
with looking at building this time with a few optimisations.

I noticed that arch/i386/Makefile uses generic -march= options.

I can have either Pentium-MMX or PentiumPro - But not Pentium2?

>From GCC 3.4.x docs:

pentium-mmx
Intel PentiumMMX CPU based on Pentium core with MMX instruction set support. 

i686, pentiumpro
Intel PentiumPro CPU. 

pentium2
Intel Pentium2 CPU based on PentiumPro core with MMX instruction set support. 

from i386/Makefile:

ifdef CONFIG_M586MMX
CFLAGS += -march=i586
endif

ifdef CONFIG_M686
CFLAGS += -march=i686
endif

ifdef CONFIG_MPENTIUMIII
CFLAGS += -march=i686
endif


Is there a specific reason why the flags aren't -march=pentium2, pentiumpro 
etc?

Also I notice that if I changed the top level Makefile to include my specific 
CPU, then the i386/Makefile adds += -march=i686 to the build lines AFTER 
CFLAGS~ thus the second one will take precedence (I guess) anyway, and the 
-march CFLAG changes are basically over-ridden?

Regards,

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

             reply	other threads:[~2005-06-05 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 13:58 Nick Warne [this message]
2005-06-05 17:43 ` CPU type .config <-> i386/Makefile question[s] Adrian Bunk
2005-06-05 19:43   ` Nick Warne

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=200506051458.50307.nick@linicks.net \
    --to=nick@linicks.net \
    --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 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.