From: kbuild test robot <fengguang.wu@intel.com>
To: Will Deacon <will.deacon@arm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: arch/ia64/kernel/ivt.S:759: Error: Operand 3 of `add' should be a general register r0-r3
Date: Sun, 11 Dec 2016 08:35:36 +0800 [thread overview]
Message-ID: <201612110823.i1ahenLO%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4301 bytes --]
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 045169816b31b10faed984b01c390db1b32ee4c1
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove HAVE_LATENCYTOP_SUPPORT
date: 11 months ago
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout da48d094ce5d7c7dcdad9011648a81c42fd1c2ef
# save the attached .config to linux build tree
make.cross ARCH=ia64
All errors (new ones prefixed by >>):
arch/ia64/kernel/ivt.S: Assembler messages:
>> arch/ia64/kernel/ivt.S:759: Error: Operand 3 of `add' should be a general register r0-r3
--
arch/ia64/kernel/entry.S: Assembler messages:
>> arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)
arch/ia64/kernel/entry.S:728: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)
arch/ia64/kernel/entry.S:859: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)
--
arch/ia64/kernel/fsys.S: Assembler messages:
>> arch/ia64/kernel/fsys.S:67: Error: Operand 3 of `add' should be a general register r0-r3
arch/ia64/kernel/fsys.S:97: Error: Operand 3 of `add' should be a general register r0-r3
arch/ia64/kernel/fsys.S:193: Error: Operand 3 of `add' should be a general register r0-r3
arch/ia64/kernel/fsys.S:336: Error: Operand 3 of `add' should be a general register r0-r3
arch/ia64/kernel/fsys.S:338: Error: Operand 3 of `add' should be a general register r0-r3
vim +759 arch/ia64/kernel/ivt.S
f8fa5448 David Mosberger-Tang 2005-04-27 743 nop.m 0 // M
f8fa5448 David Mosberger-Tang 2005-04-27 744 mov r20=r1 // A save r1
f8fa5448 David Mosberger-Tang 2005-04-27 745
f8fa5448 David Mosberger-Tang 2005-04-27 746 nop.m 0
f8fa5448 David Mosberger-Tang 2005-04-27 747 movl r30=sys_call_table // X
f8fa5448 David Mosberger-Tang 2005-04-27 748
498c5170 Isaku Yamahata 2008-05-19 749 MOV_FROM_IIP(r28) // M2 (2 cyc)
f8fa5448 David Mosberger-Tang 2005-04-27 750 cmp.eq p0,p7=r18,r17 // I0 is this a system call?
f8fa5448 David Mosberger-Tang 2005-04-27 751 (p7) br.cond.spnt non_syscall // B no ->
f8fa5448 David Mosberger-Tang 2005-04-27 752 //
f8fa5448 David Mosberger-Tang 2005-04-27 753 // From this point on, we are definitely on the syscall-path
f8fa5448 David Mosberger-Tang 2005-04-27 754 // and we can use (non-banked) scratch registers.
f8fa5448 David Mosberger-Tang 2005-04-27 755 //
f8fa5448 David Mosberger-Tang 2005-04-27 756 ///////////////////////////////////////////////////////////////////////
f8fa5448 David Mosberger-Tang 2005-04-27 757 mov r1=r16 // A move task-pointer to "addl"-addressable reg
f8fa5448 David Mosberger-Tang 2005-04-27 758 mov r2=r16 // A setup r2 for ia64_syscall_setup
f8fa5448 David Mosberger-Tang 2005-04-27 @759 add r9=TI_FLAGS+IA64_TASK_SIZE,r16 // A r9 = ¤t_thread_info()->flags
f8fa5448 David Mosberger-Tang 2005-04-27 760
f8fa5448 David Mosberger-Tang 2005-04-27 761 adds r16=IA64_TASK_THREAD_ON_USTACK_OFFSET,r16
f8fa5448 David Mosberger-Tang 2005-04-27 762 adds r15=-1024,r15 // A subtract 1024 from syscall number
^1da177e Linus Torvalds 2005-04-16 763 mov r3=NR_syscalls - 1
^1da177e Linus Torvalds 2005-04-16 764 ;;
f8fa5448 David Mosberger-Tang 2005-04-27 765 ld1.bias r17=[r16] // M0|1 r17 = current->thread.on_ustack flag
f8fa5448 David Mosberger-Tang 2005-04-27 766 ld4 r9=[r9] // M0|1 r9 = current_thread_info()->flags
f8fa5448 David Mosberger-Tang 2005-04-27 767 extr.u r8=r29,41,2 // I0 extract ei field from cr.ipsr
:::::: The code at line 759 was first introduced by commit
:::::: f8fa5448fc9b4a7806b1297a0b57808f12fe4d43 [IA64] Reschedule break_fault() for better performance.
:::::: TO: David Mosberger-Tang <davidm@hpl.hp.com>
:::::: CC: Tony Luck <tony.luck@intel.com>
---
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: 42207 bytes --]
next reply other threads:[~2016-12-11 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 0:35 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-31 18:43 kbuild test robot
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=201612110823.i1ahenLO%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@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