From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [mark:linkage/alias-rework 5/5] arch/x86/crypto/aesni-intel_asm.S:1755: Error: no such instruction: `sym_func_start_local_alias(_key_expansion_128)'
Date: Sun, 5 Dec 2021 13:17:33 +0800 [thread overview]
Message-ID: <202112051321.BwUtDKGE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git linkage/alias-rework
head: bd779ad653870d718d0df57731b1637dae509337
commit: bd779ad653870d718d0df57731b1637dae509337 [5/5] linkage: remove START/END ALIAS macros
config: x86_64-randconfig-a001-20211203 (https://download.01.org/0day-ci/archive/20211205/202112051321.BwUtDKGE-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?id=bd779ad653870d718d0df57731b1637dae509337
git remote add mark https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git
git fetch --no-tags mark linkage/alias-rework
git checkout bd779ad653870d718d0df57731b1637dae509337
# save the config file to linux build tree
mkdir build_dir
make 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 errors (new ones prefixed by >>):
arch/x86/crypto/aesni-intel_asm.S: Assembler messages:
>> arch/x86/crypto/aesni-intel_asm.S:1755: Error: no such instruction: `sym_func_start_local_alias(_key_expansion_128)'
>> arch/x86/crypto/aesni-intel_asm.S:1767: Error: invalid character '(' in mnemonic
vim +1755 arch/x86/crypto/aesni-intel_asm.S
0bd82f5f635577 Tadeusz Struk 2010-11-04 1753
0bd82f5f635577 Tadeusz Struk 2010-11-04 1754
e9b9d020c4873d Jiri Slaby 2019-10-11 @1755 SYM_FUNC_START_LOCAL_ALIAS(_key_expansion_128)
74d8b90a889022 Jiri Slaby 2019-10-11 1756 SYM_FUNC_START_LOCAL(_key_expansion_256a)
54b6a1bd5364ac Huang Ying 2009-01-18 1757 pshufd $0b11111111, %xmm1, %xmm1
54b6a1bd5364ac Huang Ying 2009-01-18 1758 shufps $0b00010000, %xmm0, %xmm4
54b6a1bd5364ac Huang Ying 2009-01-18 1759 pxor %xmm4, %xmm0
54b6a1bd5364ac Huang Ying 2009-01-18 1760 shufps $0b10001100, %xmm0, %xmm4
54b6a1bd5364ac Huang Ying 2009-01-18 1761 pxor %xmm4, %xmm0
54b6a1bd5364ac Huang Ying 2009-01-18 1762 pxor %xmm1, %xmm0
0d258efb6a58fe Mathias Krause 2010-11-27 1763 movaps %xmm0, (TKEYP)
0d258efb6a58fe Mathias Krause 2010-11-27 1764 add $0x10, TKEYP
54b6a1bd5364ac Huang Ying 2009-01-18 1765 ret
74d8b90a889022 Jiri Slaby 2019-10-11 1766 SYM_FUNC_END(_key_expansion_256a)
e9b9d020c4873d Jiri Slaby 2019-10-11 @1767 SYM_FUNC_END_ALIAS(_key_expansion_128)
54b6a1bd5364ac Huang Ying 2009-01-18 1768
:::::: The code at line 1755 was first introduced by commit
:::::: e9b9d020c4873d5e90d9986cfd137afbafbc5bfa x86/asm: Annotate aliases
:::::: TO: Jiri Slaby <jslaby@suse.cz>
:::::: CC: Borislav Petkov <bp@suse.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-05 5:18 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=202112051321.BwUtDKGE-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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).