From: Ralf Baechle <ralf@linux-mips.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Paul Burton <paul.burton@imgtec.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits
Date: Sun, 17 Apr 2016 03:19:27 +0200 [thread overview]
Message-ID: <20160417011926.GA4014@linux-mips.org> (raw)
In-Reply-To: <201604170836.kTyP1sCY%fengguang.wu@intel.com>
On Sun, Apr 17, 2016 at 08:20:38AM +0800, kbuild test robot wrote:
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 306a63bee192859ebd32c7328c7766636d882d8f
> commit: de361e8bb9f666235d44ae9770238718be4f0483 MIPS: JZ4740: introduce CONFIG_MACH_INGENIC
> date: 10 months ago
> config: mips-jz4740 (attached as .config)
> 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 de361e8bb9f666235d44ae9770238718be4f0483
> # save the attached .config to linux build tree
> make.cross ARCH=mips
>
> All errors (new ones prefixed by >>):
>
> {standard input}: Assembler messages:
> >> {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits
> {standard input}:161: Error: number (0x9000000080000000) larger than 32 bits
This is a toolchain issue afaik which I believe is the same I was seeing
a while ago on Imaginations buildbot. There it has gone away presumably
after a toolchain upgrade. Maciej, do you recall which versions were
affected?
Ralf
next prev parent reply other threads:[~2016-04-17 1:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 0:20 {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits kbuild test robot
2016-04-17 1:19 ` Ralf Baechle [this message]
2016-04-17 14:43 ` Maciej W. Rozycki
2016-04-18 13:34 ` Ralf Baechle
2016-04-18 14:25 ` Maciej W. Rozycki
2016-04-18 15:54 ` Ralf Baechle
2016-04-18 18:09 ` Maciej W. Rozycki
2016-04-19 0:25 ` Maciej W. Rozycki
2016-04-19 14:43 ` Matthew Fortune
2016-04-22 1:00 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2016-06-25 23:37 kbuild test robot
2016-06-11 23:37 kbuild test robot
2016-03-12 23:00 kbuild test robot
2016-03-05 23:09 kbuild test robot
2016-02-27 23:05 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=20160417011926.GA4014@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=paul.burton@imgtec.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