From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: {standard input}:122: Error: number (0x9000000080000000) larger than 32 bits
Date: Sun, 5 Jun 2016 07:54:07 +0800 [thread overview]
Message-ID: <201606050705.Ewv4JFXr%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Hi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 049ec1b5a76d34a6980cccdb7c0baeb4eed7a993
commit: 71458cfc782eafe4b27656e078d379a34e472adf kernel: add support for gcc 5
date: 1 year, 8 months ago
config: mips-pic32mzda_defconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
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 71458cfc782eafe4b27656e078d379a34e472adf
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
{standard input}: Assembler messages:
>> {standard input}:122: Error: number (0x9000000080000000) larger than 32 bits
{standard input}:156: Error: number (0x9000000080000000) larger than 32 bits
{standard input}:178: Error: number (0x9000000080000000) larger than 32 bits
---
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: 6419 bytes --]
next reply other threads:[~2016-06-04 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 23:54 kbuild test robot [this message]
2016-07-02 23:53 kbuild test robot
2016-07-16 22:55 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=201606050705.Ewv4JFXr%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=sasha.levin@oracle.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