diff options
author | Tiejun Chen <tiejun.chen@windriver.com> | 2013-11-22 10:49:00 +0800 |
---|---|---|
committer | Scott Wood <scottwood@freescale.com> | 2013-11-22 16:56:33 -0600 |
commit | cbf8a358be27ceecea5bd44cf82ab01683fcc90c (patch) | |
tree | ad05fcc30fd23aeca7ee60d17ac978b3ac5c036c /Documentation/atomic_ops.txt | |
parent | 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae (diff) | |
download | linux-cbf8a358be27ceecea5bd44cf82ab01683fcc90c.tar.bz2 |
powerpc/corenet64: compile with CONFIG_E{5,6}500_CPU well
If CONFIG_ALTIVEC is enabled for CoreNet64, and if we also
select CONFIG_E{5,6}500_CPU this may introduce -mcpu=e500mc64
into $CFLAGS. But Altivec option not allowed with e500mc64,
then some compiling errors occur like this:
CC arch/powerpc/lib/xor_vmx.o
arch/powerpc/lib/xor_vmx.c:1:0: error: AltiVec not supported in this target
make[1]: *** [arch/powerpc/lib/xor_vmx.o] Error 1
make: *** [arch/powerpc/lib] Error 2
So we should restrict e500mc64 in altivec scenario.
Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'Documentation/atomic_ops.txt')
0 files changed, 0 insertions, 0 deletions