Hi Peter
i have double checked this patch, it's believed that this patch
probably caused this problem
with this patch,
lizhijian@shao2-debian:~/1895/obj$ make W=1 -C source O=/home/lizhijian/1895/obj
CROSS_COMPILE=/home/lizhijian/0day/gcc-9.3.0-nolibc/or1k-linux/bin/or1k-linux- --jobs=4
ARCH=openrisc drivers/android/binder.o
make: Entering directory'/home/lizhijian/lkp/linux'
make[1]: Entering directory'/home/lizhijian/1895/obj'
GEN Makefile
UPD include/config/kernel.release
UPD include/generated/utsrelease.h
CALL /home/lizhijian/lkp/linux/scripts/atomic/check-atomics.sh
CC arch/openrisc/kernel/asm-offsets.s
CALL /home/lizhijian/lkp/linux/scripts/checksyscalls.sh
CC drivers/android/binder.o
/home/lizhijian/lkp/linux/drivers/android/binder.c: Assembler messages:
/home/lizhijian/lkp/linux/drivers/android/binder.c:3980: Error: unrecognized
keyword/register name `l.lwz ?ap,4(r20)'
/home/lizhijian/lkp/linux/drivers/android/binder.c:3985: Error: unrecognized
keyword/register name `l.addi ?ap,r0,0'
/home/lizhijian/lkp/linux/drivers/android/binder.c:3761: Error: unrecognized
keyword/register name `l.lwz ?ap,4(r20)'
/home/lizhijian/lkp/linux/drivers/android/binder.c:3766: Error: unrecognized
keyword/register name `l.addi ?ap,r0,0'
make[3]: *** [/home/lizhijian/lkp/linux/scripts/Makefile.build:267:
drivers/android/binder.o] Error 1
make[2]: *** [/home/lizhijian/lkp/linux/scripts/Makefile.build:488: drivers/android] Error
2
make[1]: *** [/home/lizhijian/lkp/linux/Makefile:1735: drivers] Error 2
make[1]: Leaving directory'/home/lizhijian/1895/obj'
make: *** [Makefile:180: sub-make] Error 2
make: Leaving directory'/home/lizhijian/lkp/linux'
reverted this patch
lizhijian@shao2-debian:~/1895/obj$ make W=1 -C source O=/home/lizhijian/1895/obj
CROSS_COMPILE=/home/lizhijian/0day/gcc-9.3.0-nolibc/or1k-linux/bin/or1k-linux- --jobs=4
ARCH=openrisc drivers/android/binder.o
make: Entering directory'/home/lizhijian/lkp/linux'
make[1]: Entering directory'/home/lizhijian/1895/obj'
GEN Makefile
UPD include/config/kernel.release
UPD include/generated/utsrelease.h
CALL /home/lizhijian/lkp/linux/scripts/atomic/check-atomics.sh
CC arch/openrisc/kernel/asm-offsets.s
CALL /home/lizhijian/lkp/linux/scripts/checksyscalls.sh
CC drivers/android/binder.o
/home/lizhijian/lkp/linux/drivers/android/binder.c:486: warning: Function parameter or
member'pid' not described in'binder_proc'
/home/lizhijian/lkp/linux/drivers/android/binder.c:486: warning: Function parameter or
member'tsk' not described in'binder_proc'
/home/lizhijian/lkp/linux/drivers/android/binder.c:549: warning: Function parameter or
member'looper_need_return' not described in'binder_thread'
/home/lizhijian/lkp/linux/drivers/android/binder.c:639: warning: Function parameter or
member'_proc' not described in'binder_proc_unlock'
/home/lizhijian/lkp/linux/drivers/android/binder.c:639: warning: Excess function
parameter'proc' description in'binder_proc_unlock'
/home/lizhijian/lkp/linux/drivers/android/binder.c:2212: warning: Function parameter or
member'file' not described in'binder_task_work_cb'
/home/lizhijian/lkp/linux/drivers/android/binder.c:2822: warning: Function parameter or
member'procp' not described in'binder_get_node_refs_for_txn'
/home/lizhijian/lkp/linux/drivers/android/binder.c:2822: warning: Excess function
parameter'proc' description in'binder_get_node_refs_for_txn'
make[1]: Leaving directory'/home/lizhijian/1895/obj'
make: Leaving directory'/home/lizhijian/lkp/linux'
And i also looked into the source code, this patch really impact buinder.c
drivers/android/binder.c -> include "drivers/android/binder_trace.h"
->include "tracepoint.h" (changed by this patch)
Thanks
Zhijian (@ 0day team)
On 6/10/20 6:04 PM, Peter Zijlstra wrote:
On Wed, Jun 10, 2020 at 09:35:11AM +0800, kernel test robot wrote:
> tree:
https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
x86/static_call
> head: c7092cb2ab86db04cf8989e6908648d134737fc1
> commit: d416f60064e5b6b65445c66fd4b6099c1a9039fb [17/19] tracepoint: Optimize using
static_call()
> config: openrisc-randconfig-r034-20200609 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout d416f60064e5b6b65445c66fd4b6099c1a9039fb
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross
ARCH=openrisc
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp(a)intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> drivers/android/binder.c: Assembler messages:
> << from drivers/android/binder.c:6196:
>>> drivers/android/binder.c:3980: Error: unrecognized keyword/register name
`l.lwz ?ap,4(r20)'
> drivers/android/binder.c:3985: Error: unrecognized keyword/register name `l.addi
?ap,r0,0'
> drivers/android/binder.c:3761: Error: unrecognized keyword/register name `l.lwz
?ap,4(r20)'
> drivers/android/binder.c:3766: Error: unrecognized keyword/register name `l.addi
?ap,r0,0'
I find it hard to believe this is the result of this patch, other than
that it might have made the compiler shit itself.
Still, I'll go update my set of cross compilers.
_______________________________________________
kbuild-all mailing list -- kbuild-all(a)lists.01.org
To unsubscribe send an email to kbuild-all-leave(a)lists.01.org