From: kbuild test robot <fengguang.wu@intel.com>
To: Daniel Micay <danielmicay@gmail.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 216/292] arch/sparc/include/asm/string.h:22:2: error: expected identifier or '(' before '{' token
Date: Sat, 3 Jun 2017 10:50:03 +0800 [thread overview]
Message-ID: <201706031050.ACPBz4zP%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 5c84fce56580d5297cd473b57f893e362b332109
commit: abb4387dc4c5898e87a93f152d3ad4b991397f22 [216/292] include/linux/string.h: add the option of fortified string.h functions
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout abb4387dc4c5898e87a93f152d3ad4b991397f22
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
In file included from include/linux/string.h:18:0,
from include/linux/bitmap.h:8,
from include/linux/cpumask.h:11,
from include/linux/rcupdate.h:40,
from include/linux/rculist.h:10,
from include/linux/pid.h:4,
from include/linux/sched.h:13,
from arch/sparc/kernel/asm-offsets.c:13:
>> arch/sparc/include/asm/string.h:22:2: error: expected identifier or '(' before '{' token
({ \
^
include/linux/string.h:332:24: note: in expansion of macro 'memscan'
__FORTIFY_INLINE void *memscan(void *p, int c, __kernel_size_t size)
^~~~~~~
make[2]: *** [arch/sparc/kernel/asm-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +22 arch/sparc/include/asm/string.h
70a6fcf3 Al Viro 2016-01-17 16 #define __HAVE_ARCH_MEMSET
70a6fcf3 Al Viro 2016-01-17 17 #define memset(s, c, count) __builtin_memset(s, c, count)
70a6fcf3 Al Viro 2016-01-17 18
70a6fcf3 Al Viro 2016-01-17 19 #define __HAVE_ARCH_MEMSCAN
70a6fcf3 Al Viro 2016-01-17 20
70a6fcf3 Al Viro 2016-01-17 21 #define memscan(__arg0, __char, __arg2) \
70a6fcf3 Al Viro 2016-01-17 @22 ({ \
70a6fcf3 Al Viro 2016-01-17 23 void *__memscan_zero(void *, size_t); \
70a6fcf3 Al Viro 2016-01-17 24 void *__memscan_generic(void *, int, size_t); \
70a6fcf3 Al Viro 2016-01-17 25 void *__retval, *__addr = (__arg0); \
:::::: The code at line 22 was first introduced by commit
:::::: 70a6fcf3283a0ac1e11737c6d90c0753f9824e9d [sparc] unify 32bit and 64bit string.h
:::::: TO: Al Viro <viro@zeniv.linux.org.uk>
:::::: CC: Al Viro <viro@zeniv.linux.org.uk>
---
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: 50518 bytes --]
reply other threads:[~2017-06-03 2:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201706031050.ACPBz4zP%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--cc=hannes@cmpxchg.org \
--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;
as well as URLs for NNTP newsgroup(s).