From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [tip:x86/core 53/53] arch/x86/crypto/chacha-x86_64.prelink.o: warning: objtool: chacha_2block_xor_avx512vl() falls through to next function chacha_8block_xor_avx512vl()
Date: Sat, 19 Mar 2022 20:07:19 +0800 [thread overview]
Message-ID: <202203192005.hZMAnkDH-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
CC: x86@kernel.org
TO: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/core
head: 2f35e67f621fffc636cb802a4f93fd168cf38274
commit: 2f35e67f621fffc636cb802a4f93fd168cf38274 [53/53] kbuild: Fixup the IBT kbuild changes
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20220319/202203192005.hZMAnkDH-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a6e70e4056dff962ec634c5bd4f2f4105a0bef71)
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
# https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=2f35e67f621fffc636cb802a4f93fd168cf38274
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip x86/core
git checkout 2f35e67f621fffc636cb802a4f93fd168cf38274
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/
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 >>):
>> arch/x86/crypto/chacha-x86_64.prelink.o: warning: objtool: chacha_2block_xor_avx512vl() falls through to next function chacha_8block_xor_avx512vl()
>> arch/x86/crypto/chacha-x86_64.prelink.o: warning: objtool: chacha_4block_xor_avx512vl() falls through to next function chacha_8block_xor_avx512vl()
--
>> arch/x86/crypto/poly1305-x86_64.prelink.o: warning: objtool: poly1305_blocks_avx() falls through to next function poly1305_blocks_x86_64()
>> arch/x86/crypto/poly1305-x86_64.prelink.o: warning: objtool: poly1305_emit_avx() falls through to next function poly1305_emit_x86_64()
>> arch/x86/crypto/poly1305-x86_64.prelink.o: warning: objtool: poly1305_blocks_avx2() falls through to next function poly1305_blocks_x86_64()
>> arch/x86/crypto/poly1305-x86_64.prelink.o: warning: objtool: poly1305_blocks_avx512() falls through to next function poly1305_blocks_x86_64()
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-19 12:08 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=202203192005.hZMAnkDH-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
/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.