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/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)
Date: Sun, 14 Aug 2016 15:27:35 +0800 [thread overview]
Message-ID: <201608141529.e6jiTOoH%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3870 bytes --]
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 118253a593bd1c57de2d1193df1ccffe1abe745b
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove HAVE_LATENCYTOP_SUPPORT
date: 7 months ago
config: ia64-allyesconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 4.9.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/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
--
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
vim +621 arch/ia64/kernel/entry.S
^1da177e Linus Torvalds 2005-04-16 605 PT_REGS_UNWIND_INFO(0)
^1da177e Linus Torvalds 2005-04-16 606 { /*
^1da177e Linus Torvalds 2005-04-16 607 * Some versions of gas generate bad unwind info if the first instruction of a
^1da177e Linus Torvalds 2005-04-16 608 * procedure doesn't go into the first slot of a bundle. This is a workaround.
^1da177e Linus Torvalds 2005-04-16 609 */
^1da177e Linus Torvalds 2005-04-16 610 nop.m 0
^1da177e Linus Torvalds 2005-04-16 611 nop.i 0
^1da177e Linus Torvalds 2005-04-16 612 /*
^1da177e Linus Torvalds 2005-04-16 613 * We need to call schedule_tail() to complete the scheduling process.
^1da177e Linus Torvalds 2005-04-16 614 * Called by ia64_switch_to() after do_fork()->copy_thread(). r8 contains the
^1da177e Linus Torvalds 2005-04-16 615 * address of the previously executing task.
^1da177e Linus Torvalds 2005-04-16 616 */
^1da177e Linus Torvalds 2005-04-16 617 br.call.sptk.many rp=ia64_invoke_schedule_tail
^1da177e Linus Torvalds 2005-04-16 618 }
^1da177e Linus Torvalds 2005-04-16 619 .ret8:
54d496c3 Al Viro 2012-10-14 620 (pKStk) br.call.sptk.many rp=call_payload
^1da177e Linus Torvalds 2005-04-16 @621 adds r2=TI_FLAGS+IA64_TASK_SIZE,r13
^1da177e Linus Torvalds 2005-04-16 622 ;;
^1da177e Linus Torvalds 2005-04-16 623 ld4 r2=[r2]
^1da177e Linus Torvalds 2005-04-16 624 ;;
^1da177e Linus Torvalds 2005-04-16 625 mov r8=0
^1da177e Linus Torvalds 2005-04-16 626 and r2=_TIF_SYSCALL_TRACEAUDIT,r2
^1da177e Linus Torvalds 2005-04-16 627 ;;
^1da177e Linus Torvalds 2005-04-16 628 cmp.ne p6,p0=r2,r0
^1da177e Linus Torvalds 2005-04-16 629 (p6) br.cond.spnt .strace_check_retval
:::::: The code at line 621 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 45017 bytes --]
next reply other threads:[~2016-08-14 9:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 7:27 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 1:03 arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191) kbuild test robot
2017-01-01 5:53 kbuild test robot
2016-12-25 2:42 kbuild test robot
2016-11-20 9:11 kbuild test robot
2016-11-13 0:36 kbuild test robot
2016-11-06 0:20 kbuild test robot
2016-10-30 5:05 kbuild test robot
2016-10-23 2:48 kbuild test robot
2016-10-02 6:10 kbuild test robot
2016-09-22 7:45 kbuild test robot
2016-09-11 1:10 kbuild test robot
2016-09-04 20:34 kbuild test robot
2016-06-26 4:14 kbuild test robot
2016-06-26 4:14 ` kbuild test robot
2016-06-05 11:35 kbuild test robot
2016-06-05 11:35 ` kbuild test robot
2016-04-18 5:16 kbuild test robot
2016-03-20 20:03 kbuild test robot
2016-03-21 10:38 ` Will Deacon
2016-03-21 10:38 ` Will Deacon
2016-03-06 13:47 kbuild test robot
2016-03-09 16:03 ` Will Deacon
2016-03-09 16:03 ` Will Deacon
2016-02-28 12:09 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=201608141529.e6jiTOoH%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 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.