Skip to contentSkip to conversation

CPU type .config <-> i386/Makefile question[s]

DISCUSSION Nick Warne 2 participants 3 messages Jun 5, 2005

lore
Share & tools
lore

Nick Warne

author
#0 lore 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?

Quoted 1 line

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

Signature · 2 lines
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
#1 lore raw
Quoted 1 line · Nick Warne

Hello all,

Hi Nick,

Quoted 8 lines

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.
...
Is there a specific reason why the flags aren't -march=pentium2, pentiumpro etc?

the specific reason is that kernel 2.4 is in a maintainance mode and such changes are not considered being worth the risk of breaking anything anywhere with any of the supported gcc versions.

In kernel 2.6, this is already handled the way you expect it.

Quoted 4 lines

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?

Users are not expected to manually set any CFLAGS.

It might work in your case, but unless you _really_ know what you are doing you always risk some breakage.

Quoted 3 lines

Regards,

Nick

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
author
#2 lore raw
Quoted 11 lines · Adrian Bunk

the specific reason is that kernel 2.4 is in a maintainance mode and such changes are not considered being worth the risk of breaking anything anywhere with any of the supported gcc versions.

In kernel 2.6, this is already handled the way you expect it.

Quoted 4 lines

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?

Quoted 4 lines

Users are not expected to manually set any CFLAGS.

It might work in your case, but unless you _really_ know what you are doing you always risk some breakage.

I see! Thanks for info. I can do my own patch to play with :-)

Nick

Signature · 2 lines
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."