> I think when GCC supports the different cores, it should be supported by the
> kernel scripts, the differences between the cores are real enough to have
> potential optimizations at least in theory (as far as I could see the only
> difference in GCC 3.2 is whether to use SSE, but that could change in the
To use SSE in kernel space, we need to wrap it in kernel_fpu_begin() /
kernel_fpu_end() pairs anyway. gcc doesn't (and can't) know this.
> I think it's a fairly simple patch that doesn't break anything
it's non-obvious that it'll break things when people use broken compilers.
read what I wrote before, several gcc versions got this horribly wrong.
"athlon4" was even tuned for 64bit at one point.
Take away the SSE, take away the broken compiler versions, and you'd be
left with something that would hardly show a blip on a benchmark.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/