From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [luto:x86/fixes 21/26] arch/x86/entry/entry_32.S:819: Error: bad register name `%rsp'
Date: Tue, 02 Mar 2021 15:48:34 +0800 [thread overview]
Message-ID: <202103021532.VpyRqfdV-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/fixes
head: 5a71c0b98407b8fc659967e261ce84da00270892
commit: b529690d96d16fa95b3e6f7baed3f303d01e962c [21/26] x86/entry: Convert ret_from_fork to C
config: i386-randconfig-s002-20210302 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-241-geaceeafa-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?id=b529690d96d16fa95b3e6f7baed3f303d01e962c
git remote add luto https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
git fetch --no-tags luto x86/fixes
git checkout b529690d96d16fa95b3e6f7baed3f303d01e962c
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
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/entry/entry_32.S: Assembler messages:
>> arch/x86/entry/entry_32.S:819: Error: bad register name `%rsp'
arch/x86/entry/entry_32.S:821: Error: bad register name `%rsp'
vim +819 arch/x86/entry/entry_32.S
807
808 /*
809 * A newly forked process directly context switches into this address.
810 *
811 * eax: prev task we switched from
812 * ebx: kernel thread func (NULL for user thread)
813 * edi: kernel thread arg
814 */
815 .pushsection .text, "ax"
816 SYM_CODE_START(asm_ret_from_fork)
817 movl %ebx, %edx
818 movl %edi, %ecx
> 819 pushl %rsp
820 call ret_from_fork
821 addl $4, %rsp
822 jmp .Lsyscall_32_done
823 SYM_CODE_END(asm_ret_from_fork)
824 .popsection
825
---
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: 33903 bytes --]
reply other threads:[~2021-03-02 7:48 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=202103021532.VpyRqfdV-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.