No. We went through this already. Programs might need different
initialization values and the value the kernel/libc uses might also
change. I son't want to encode anywhere a value which would tie a
glibc version to a specific kernel version. The patch is minimal,
introduces almost no costs and it helps in every situation to
determine whether the default behaviour is the one wanted.
Ulrich you're insane, listen again:
"The kernel initial fpu cw setting will never change on any
architecture, it is cast in stone forever."
Therefore if you minimally don't do something like:
if (fpucw_we_need != KERNEL_DEFAULT_FPU_CW)
__setfpucw(fpucw_we_need);
You're just being rediculious about all this.
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/