From: kernel test robot <lkp@intel.com>
To: Vasily Gorbik <gor@linux.ibm.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: kbuild-all@lists.01.org, Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86 <x86@kernel.org>
Subject: Re: [PATCH 1/1] x86/tools: Use tools headers for instruction decoder selftests
Date: Wed, 4 Nov 2020 19:54:24 +0800 [thread overview]
Message-ID: <202011041940.xqazT0Kv-lkp@intel.com> (raw)
In-Reply-To: <patch-1.thread-59328d.git-59328d9dc2b9.your-ad-here.call-01604429777-ext-1374@work.hours>
[-- Attachment #1: Type: text/plain, Size: 3207 bytes --]
Hi Vasily,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v5.10-rc2 next-20201103]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Vasily-Gorbik/x86-tools-Use-tools-headers-for-instruction-decoder-selftests/20201104-043600
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 238c91115cd05c71447ea071624a4c9fe661f970
config: x86_64-randconfig-s022-20201103 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-76-gf680124b-dirty
# https://github.com/0day-ci/linux/commit/ab4952becdfae8a76a6f0e0fb4ec7d078e80d5d6
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Vasily-Gorbik/x86-tools-Use-tools-headers-for-instruction-decoder-selftests/20201104-043600
git checkout ab4952becdfae8a76a6f0e0fb4ec7d078e80d5d6
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from arch/x86/tools/insn_sanity.c:19:
tools/arch/x86/lib/insn.c: In function '__insn_get_emulate_prefix':
>> tools/arch/x86/lib/insn.c:32:9: warning: implicit declaration of function 'unlikely' [-Wimplicit-function-declaration]
32 | ({ if (unlikely(!validate_next(t, insn, n))) goto err_out; __peek_nbyte_next(t, insn, n); })
| ^~~~~~~~
tools/arch/x86/lib/insn.c:72:7: note: in expansion of macro 'peek_nbyte_next'
72 | if (peek_nbyte_next(insn_byte_t, insn, i) != prefix[i])
| ^~~~~~~~~~~~~~~
arch/x86/tools/insn_sanity.c: In function 'read_next_insn':
>> arch/x86/tools/insn_sanity.c:128:19: warning: implicit declaration of function 'ARRAY_SIZE' [-Wimplicit-function-declaration]
128 | tmp = fgets(buf, ARRAY_SIZE(buf), input_file);
| ^~~~~~~~~~
/usr/bin/ld: /tmp/ccO69OOl.o: in function `__insn_get_emulate_prefix.constprop.0':
>> insn_sanity.c:(.text+0x417): undefined reference to `unlikely'
/usr/bin/ld: /tmp/ccO69OOl.o: in function `insn_get_prefixes':
insn_sanity.c:(.text+0x647): undefined reference to `unlikely'
>> /usr/bin/ld: insn_sanity.c:(.text+0x6b7): undefined reference to `unlikely'
/usr/bin/ld: insn_sanity.c:(.text+0x744): undefined reference to `unlikely'
/usr/bin/ld: insn_sanity.c:(.text+0x77f): undefined reference to `unlikely'
/usr/bin/ld: /tmp/ccO69OOl.o:insn_sanity.c:(.text+0x817): more undefined references to `unlikely' follow
/usr/bin/ld: /tmp/ccO69OOl.o: in function `main':
>> insn_sanity.c:(.text.startup+0x48a): undefined reference to `ARRAY_SIZE'
collect2: error: ld returned 1 exit status
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33892 bytes --]
prev parent reply other threads:[~2020-11-04 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 16:20 [tip: objtool/core] x86/insn: Support big endian cross-compiles tip-bot2 for Martin Schwidefsky
2020-10-09 20:38 ` Peter Zijlstra
2020-10-09 20:49 ` Borislav Petkov
2020-10-10 14:02 ` Vasily Gorbik
2020-10-11 14:40 ` Borislav Petkov
2020-10-12 0:02 ` Masami Hiramatsu
2020-10-10 17:44 ` Josh Poimboeuf
2020-10-12 0:12 ` Masami Hiramatsu
2020-10-12 15:39 ` Josh Poimboeuf
2020-10-14 7:28 ` Masami Hiramatsu
2020-10-15 6:24 ` Ian Rogers
2020-11-03 19:35 ` Vasily Gorbik
2020-11-03 19:35 ` [PATCH 1/1] x86/tools: Use tools headers for instruction decoder selftests Vasily Gorbik
2020-11-04 9:11 ` kernel test robot
2020-11-04 9:18 ` Vasily Gorbik
2020-11-06 2:24 ` Masami Hiramatsu
2020-11-06 17:52 ` Josh Poimboeuf
2020-11-04 11:54 ` kernel test robot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202011041940.xqazT0Kv-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=gor@linux.ibm.com \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox