You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Benjamin Herrenschmidt 52292c9b8c [PATCH] ppc64: fix gcc 4.0 vs CONFIG_ALTIVEC ... gcc-4.0 generates altivec code implicitly when -mcpu indicates an altivec capable CPU which is not suitable for the kernel. However, we used to set -mcpu=970 when CONFIG_ALTIVEC was set because a gcc-3.x bug prevented from using -maltivec along with -mcpu=power4, thus prevented building the RAID6 altivec code. This patch fixes all of this by testing for the gcc version. If 4.0 or later, just normally use -mcpu=power4 and let the RAID6 code add -maltivec to the few files it needs to be compiled with altivec support. For 3.x, we still use -mcpu=970 to work around the above problem, which is fine as 3.x will never implicitly generate altivec code. The Makefile hackery may not be the most lovely, I welcome anybody more skilled than me to improve it. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		20 years ago
..
boot	[PATCH] ppc64: tell firmware about kernel capabilities	20 years ago
configs	…
kernel	[PATCH] convert that currently tests _NSIG directly to use valid_signal()	20 years ago
lib	…
mm	[PATCH] PPC64: Remove hot busy-wait loop in __hash_page	20 years ago
oprofile	…
xmon	[PATCH] ppc-opc NULL noise removal	20 years ago
Kconfig	…
Kconfig.debug	…
Makefile	[PATCH] ppc64: fix gcc 4.0 vs CONFIG_ALTIVEC	20 years ago
defconfig	…