From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kees:kspp/memcpy/next-20210618/v0 54/82] arch/s390/boot/../lib/string.c:11:9: warning: '__NO_FORTIFY' macro redefined
Date: Sat, 19 Jun 2021 19:47:12 +0800 [thread overview]
Message-ID: <202106191905.vm6wpDUn-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git kspp/memcpy/next-20210618/v0
head: fd2aa2a169de8bde9502e7a2fc48cd03d4bfd996
commit: 245fccabb5777708f67afa04fc6b99a3f794986f [54/82] lib/string: Move helper functions out of string.c
config: s390-randconfig-r034-20210618 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d1baf2895467735ab14f4b3415fce204c0cc8e7f)
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
# install s390 cross compiling tool for clang build
# apt-get install binutils-s390x-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=245fccabb5777708f67afa04fc6b99a3f794986f
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees kspp/memcpy/next-20210618/v0
git checkout 245fccabb5777708f67afa04fc6b99a3f794986f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=s390
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from arch/s390/boot/string.c:7:
>> arch/s390/boot/../lib/string.c:11:9: warning: '__NO_FORTIFY' macro redefined [-Wmacro-redefined]
#define __NO_FORTIFY
^
<command line>:4:9: note: previous definition is here
#define __NO_FORTIFY 1
^
1 warning generated.
--
In file included from arch/s390/boot/string.c:7:
>> arch/s390/boot/../lib/string.c:11:9: warning: '__NO_FORTIFY' macro redefined [-Wmacro-redefined]
#define __NO_FORTIFY
^
<command line>:5:9: note: previous definition is here
#define __NO_FORTIFY 1
^
1 warning generated.
vim +/__NO_FORTIFY +11 arch/s390/boot/../lib/string.c
> 11 #define __NO_FORTIFY
12
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 17961 bytes --]
reply other threads:[~2021-06-19 11:47 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=202106191905.vm6wpDUn-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.