All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	Paul Burton <paul.burton@imgtec.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits
Date: Sun, 17 Apr 2016 15:43:49 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1604171535550.28036@eddie.linux-mips.org> (raw)
In-Reply-To: <20160417011926.GA4014@linux-mips.org>

Ralf,

> > 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?

 I've been wondering about these errors too as I have never come across 
them myself.  So I have no idea what's causing them and I can't really 
help other than maybe running `git bisect' on binutils sometime.  Or is 
there a way to get the version of GAS involved? -- `as --version' will do.  
I could see if I could build it and reproduce the problem to see what's 
causing it.  Also seeing the offending .s file could help too, i.e. 
knowing what the context is here.

  Maciej

  reply	other threads:[~2016-04-17 14:43 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
2016-04-17 14:43   ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.20.1604171535550.28036@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.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 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.