Re: Possibility of adding -march=native to x86

[Michael Lothian]

> > Half the time it's easier doing a lsmod when booted on a livecd and
> > trying to figure out what options are required from the module names
> > which sometime can be just as tricky.
>
> Sure, distributions already have solved this and you can use their
> work.

I like compiling my own kernel it's just a pain doing it the first
time on a new motherboard or when adding a new piece of hardware

> > Maybe even having a make addnewhardware option to quickly add extra
> > devices to your config file.
>
> Knowing your CPU is much easier to figure out than to figure out the
> BIOS settings of your SATA controller that determine how to access it.

So how do distro's figure out which driver to use? Isn't it a matter
of taking the pci-ids and selecting the correct driver?

> If you do not even know what CPU you have you should really not compile
> your own kernel.

It about ease of use, look at the new core2 architecture, if your gcc
is new enough there is a march=core2 else you use an older flag

Same with the new cell architecture you use cell if your using gcc 4.3
alpha or 930 if it's not that new.

What I'm saying is sometimes GCC or the Kernel is better at making
these decisions or at least make it easier

Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/