From: kbuild test robot <lkp@intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: kbuild-all@01.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
x86@vger.kernel.org, linux@rasmusvillemoes.dk,
torvalds@linux-foundation.org
Subject: Re: [PATCH] x86_64: new and improved memset()
Date: Mon, 16 Sep 2019 16:43:05 +0800 [thread overview]
Message-ID: <201909161637.hjotmWPv%lkp@intel.com> (raw)
In-Reply-To: <20190914103345.GA5856@avx2>
[-- Attachment #1: Type: text/plain, Size: 4645 bytes --]
Hi Alexey,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190915]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Alexey-Dobriyan/x86_64-new-and-improved-memset/20190916-140315
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=um SUBARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
/usr/bin/ld: arch/um/kernel/mem.o: in function `pgd_alloc':
>> mem.c:(.text+0x4a): undefined reference to `memset0_mov'
/usr/bin/ld: arch/um/kernel/mem.o: in function `pmd_alloc_one':
>> mem.c:(.text+0xd1): undefined reference to `_memset0_mov'
/usr/bin/ld: arch/um/kernel/mem.o: in function `mem_init':
>> mem.c:(.init.text+0x20): undefined reference to `_memset0_mov'
>> /usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0x1): undefined reference to `_memset0_rep_stosq'
>> /usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0x6): undefined reference to `memset0_rep_stosb'
>> /usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0xb): undefined reference to `memset0_rep_stosq'
/usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0x10): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0x15): undefined reference to `_memset0_rep_stosq'
/usr/bin/ld: arch/um/kernel/mem.o:(.altinstr_replacement+0x1a): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/kernel/process.o: in function `copy_from_user_proc':
>> process.c:(.text+0x665): undefined reference to `memset0_mov'
/usr/bin/ld: arch/um/kernel/process.o: in function `sysemu_proc_write':
process.c:(.text+0x76a): undefined reference to `memset0_mov'
>> /usr/bin/ld: arch/um/kernel/process.o:(.altinstr_replacement+0x1): undefined reference to `memset0_rep_stosq'
>> /usr/bin/ld: arch/um/kernel/process.o:(.altinstr_replacement+0x6): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/kernel/process.o:(.altinstr_replacement+0xb): undefined reference to `memset0_rep_stosq'
/usr/bin/ld: arch/um/kernel/process.o:(.altinstr_replacement+0x10): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/drivers/net_kern.o: in function `eth_configure':
>> net_kern.c:(.text+0xbd0): undefined reference to `memset0_mov'
>> /usr/bin/ld: arch/um/drivers/net_kern.o:(.altinstr_replacement+0x1): undefined reference to `memset0_rep_stosq'
>> /usr/bin/ld: arch/um/drivers/net_kern.o:(.altinstr_replacement+0x6): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/drivers/ubd_kern.o: in function `ubd_ioctl':
>> ubd_kern.c:(.text+0x984): undefined reference to `_memset0_mov'
>> /usr/bin/ld: ubd_kern.c:(.text+0xa5a): undefined reference to `memset0_mov'
/usr/bin/ld: arch/um/drivers/ubd_kern.o: in function `io_thread':
>> ubd_kern.c:(.text+0x211f): undefined reference to `memset0_mov'
>> /usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0x1): undefined reference to `_memset0_rep_stosq'
>> /usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0x6): undefined reference to `memset0_rep_stosb'
>> /usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0xb): undefined reference to `memset0_rep_stosq'
/usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0x10): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0x15): undefined reference to `memset0_rep_stosq'
/usr/bin/ld: arch/um/drivers/ubd_kern.o:(.altinstr_replacement+0x1a): undefined reference to `memset0_rep_stosb'
/usr/bin/ld: kernel/fork.o: in function `copy_clone_args_from_user':
>> fork.c:(.text+0x5c4): undefined reference to `memset0_mov'
/usr/bin/ld: kernel/fork.o: in function `mm_init.isra.5':
>> fork.c:(.text+0x75c): undefined reference to `_memset0_mov'
/usr/bin/ld: kernel/fork.o: in function `vm_area_alloc':
fork.c:(.text+0xaa4): undefined reference to `_memset0_mov'
/usr/bin/ld: kernel/fork.o: in function `mm_alloc':
fork.c:(.text+0xb9f): undefined reference to `_memset0_mov'
/usr/bin/ld: kernel/fork.o: in function `copy_process':
fork.c:(.text+0x1e0c): undefined reference to `_memset0_mov'
---
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: 8262 bytes --]
next prev parent reply other threads:[~2019-09-16 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 10:33 Alexey Dobriyan
2019-09-14 11:37 ` Borislav Petkov
2019-09-14 15:15 ` Alexey Dobriyan
2019-09-16 7:54 ` kbuild test robot
2019-09-16 8:43 ` kbuild test robot [this message]
2019-09-16 14:18 ` David Laight
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=201909161637.hjotmWPv%lkp@intel.com \
--to=lkp@intel.com \
--cc=adobriyan@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@vger.kernel.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
Powered by JetHome