From: kbuild test robot <fengguang.wu@intel.com>
To: Clement Courbet <courbet@google.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 2148/2944] lib/find_bit_benchmark.c:115:7: error: implicit declaration of function 'find_next_and_bit'; did you mean 'find_next_bit'?
Date: Tue, 5 Dec 2017 20:31:28 +0800 [thread overview]
Message-ID: <201712052024.0kVygoFI%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7ceb97a071e80f1b5e4cd5a36de135612a836388
commit: e49c614e6b37254b1e7bf55c631ce3cb5e3b6433 [2148/2944] lib: optimize cpumask_next_and()
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout e49c614e6b37254b1e7bf55c631ce3cb5e3b6433
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
lib/find_bit_benchmark.c: In function 'test_find_next_and_bit':
>> lib/find_bit_benchmark.c:115:7: error: implicit declaration of function 'find_next_and_bit'; did you mean 'find_next_bit'? [-Werror=implicit-function-declaration]
i = find_next_and_bit(bitmap, bitmap2, BITMAP_LEN, i+1);
^~~~~~~~~~~~~~~~~
find_next_bit
cc1: some warnings being treated as errors
vim +115 lib/find_bit_benchmark.c
106
107 static int __init test_find_next_and_bit(const void *bitmap,
108 const void *bitmap2, unsigned long len)
109 {
110 unsigned long i, cnt;
111 cycles_t cycles;
112
113 cycles = get_cycles();
114 for (cnt = i = 0; i < BITMAP_LEN; cnt++)
> 115 i = find_next_and_bit(bitmap, bitmap2, BITMAP_LEN, i+1);
116 cycles = get_cycles() - cycles;
117 pr_err("find_next_and_bit: %ld cycles, %ld iterations\n", (long)cycles,
118 cnt);
119
120 return 0;
121 }
122
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45145 bytes --]
next reply other threads:[~2017-12-05 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 12:31 kbuild test robot [this message]
2017-12-06 0:09 ` Andrew Morton
2017-12-06 8:42 ` Geert Uytterhoeven
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=201712052024.0kVygoFI%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=courbet@google.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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