| commit | 0197cd2e350a7151080e7335577e956f1f84a8cb | |
| author | Kumar Gala <galak@kernel.crashing.org> | |
| Thu, 18 Oct 2007 21:53:19 +0000 (18 16:53 -0500) | ||
| committer | Kumar Gala <galak@kernel.crashing.org> | |
| Fri, 9 Nov 2007 09:47:29 +0000 (9 03:47 -0600) | ||
| tree | 4ac1a37fbb9a8b8ec6c98f3d692bcd18c8b439b2 | treesnapshot (tar.gz zip) |
| parent | 688016f4e2028e3c2c27e959ad001536e10ee2c5 | commitdiff |
[POWERPC] Add -mno-spe for ARCH=powerpc builds
Newer GCC's are capable of autovectorization for ISA extensions like
AltiVec and SPE. If we happen to build with one of those compilers we
will get SPE instructions in random kernel code. Today we only allow
basic interger code in the kernel and FP, AltiVec, or SPE in special
explicit locations that have handled the proper saving and restoring of
the register state (since on uniprocessor we lazy context switch the
register state for FP, AltiVec, and SPE).
-mno-spe disables the compiler for automatically generating SPE
instructions without our knowledge.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Newer GCC's are capable of autovectorization for ISA extensions like
AltiVec and SPE. If we happen to build with one of those compilers we
will get SPE instructions in random kernel code. Today we only allow
basic interger code in the kernel and FP, AltiVec, or SPE in special
explicit locations that have handled the proper saving and restoring of
the register state (since on uniprocessor we lazy context switch the
register state for FP, AltiVec, and SPE).
-mno-spe disables the compiler for automatically generating SPE
instructions without our knowledge.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
| arch/powerpc/Makefile | diffblobblamehistory |