From: Will Deacon <will.deacon@arm.com>
To: kbuild test robot <fengguang.wu@intel.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: Re: arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191)
Date: Wed, 9 Mar 2016 16:03:26 +0000 [thread overview]
Message-ID: <20160309160325.GH28496@arm.com> (raw)
In-Reply-To: <201603062105.9tHMvN5r%fengguang.wu@intel.com>
On Sun, Mar 06, 2016 at 09:47:10PM +0800, kbuild test robot wrote:
> FYI, the error/warning still remains.
[...]
> 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
Yeah :( I reported this on linux-arch a while back:
http://lkml.kernel.org/r/20160127150031.GI2390@arm.com
but didn't get any replies (I cc'd the maintainers).
Tell you what; I'll repost the fix I had there (basically disabling
LATENCYTOP for ia64) as a separate patch and see how it goes.
Will
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-03-09 16:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 13:47 arch/ia64/kernel/entry.S:621: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191) kbuild test robot
2016-03-09 16:03 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 1:03 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-08-14 7:27 kbuild test robot
2016-06-26 4:14 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-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=20160309160325.GH28496@arm.com \
--to=will.deacon@arm.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).