32-bit poweroc compile failure in v4.19-rc7-166-g7ec21823634d
From: Meelis Roos
Date: Sat Oct 13 2018 - 16:39:12 EST
I tried to test the fix to 32-bit poweroc boot hang but found that current git does not compile on 32bit poweroc at all for me:
CC arch/powerpc/kernel/ptrace.o
In file included from ./include/linux/bitmap.h:9,
from ./include/linux/cpumask.h:12,
from ./include/linux/rcupdate.h:44,
from ./include/linux/rculist.h:11,
from ./include/linux/pid.h:5,
from ./include/linux/sched.h:14,
from arch/powerpc/kernel/ptrace.c:19:
In function âmemcpyâ,
inlined from âuser_regset_copyinâ at ./include/linux/regset.h:295:4,
inlined from âvr_setâ at arch/powerpc/kernel/ptrace.c:619:9:
./include/linux/string.h:345:9: error: â__builtin_memcpyâ offset [-527, -529] is out of the bounds [0, 16] of object âvrsaveâ with type âunion <anonymous>â [-Werror=array-bounds]
return __builtin_memcpy(p, q, size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/kernel/ptrace.c: In function âvr_setâ:
arch/powerpc/kernel/ptrace.c:614:5: note: âvrsaveâ declared here
} vrsave;
^~~~~~
In file included from ./include/linux/bitmap.h:9,
from ./include/linux/cpumask.h:12,
from ./include/linux/rcupdate.h:44,
from ./include/linux/rculist.h:11,
from ./include/linux/pid.h:5,
from ./include/linux/sched.h:14,
from arch/powerpc/kernel/ptrace.c:19:
In function âmemcpyâ,
inlined from âuser_regset_copyoutâ at ./include/linux/regset.h:270:4,
inlined from âvr_getâ at arch/powerpc/kernel/ptrace.c:572:9:
./include/linux/string.h:345:9: error: â__builtin_memcpyâ offset [-527, -529] is out of the bounds [0, 16] of object âvrsaveâ with type âunion <anonymous>â [-Werror=array-bounds]
return __builtin_memcpy(p, q, size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/kernel/ptrace.c: In function âvr_getâ:
arch/powerpc/kernel/ptrace.c:567:5: note: âvrsaveâ declared here
} vrsave;
^~~~~~
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:306: arch/powerpc/kernel/ptrace.o] Error 1
make: *** [Makefile:1052: arch/powerpc/kernel] Error 2
--
Meelis Roos <mroos@xxxxxxxx>