From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
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: Mon, 18 Apr 2016 17:54:40 +0200 [thread overview]
Message-ID: <20160418155440.GC24051@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1604181514240.21846@tp.orcam.me.uk>
On Mon, Apr 18, 2016 at 03:25:56PM +0100, Maciej W. Rozycki wrote:
> On Mon, 18 Apr 2016, Ralf Baechle wrote:
>
> > The old case btw, affects ip22 with a random_config:
> >
> > CC arch/mips/mm/sc-ip22.o
> > {standard input}: Assembler messages:
> > {standard input}:137: Error: number (0x9000000080000000) larger than 32 bits
> > {standard input}:162: Error: number (0x9000000080000000) larger than 32 bits
> > scripts/Makefile.build:258: recipe for target 'arch/mips/mm/sc-ip22.o' failed
> > make[2]: *** [arch/mips/mm/sc-ip22.o] Error 1
> > scripts/Makefile.build:403: recipe for target 'arch/mips/mm' failed
> > make[1]: *** [arch/mips/mm] Error 2
> > Makefile:947: recipe for target 'arch/mips' failed
> > make: *** [arch/mips] Error 2
> >
> > and I was able to reproduce it with binutils 2.26 and commit
> > c517d838eb7d07bbe9507871fab3931deccff539 ("Linux 4.0-rc1"). The code
> > in question looks like:
> >
> > static inline void indy_sc_wipe(unsigned long first, unsigned long last)
> > {
> > unsigned long tmp;
> >
> > __asm__ __volatile__(
> > ".set\tpush\t\t\t# indy_sc_wipe\n\t"
> > ".set\tnoreorder\n\t"
> > ".set\tmips3\n\t"
> > ".set\tnoat\n\t"
> > "mfc0\t%2, $12\n\t"
> > "li\t$1, 0x80\t\t\t# Go 64 bit\n\t"
> > "mtc0\t$1, $12\n\t"
> >
> > "dli\t$1, 0x9000000080000000\n\t"
>
> That does not help me, I'm afraid, I can't trigger the issue with this
> piece of code alone. It may be caused by a particular combination of GAS
> command line options and `.set' directives.
>
> Since you can reproduce it, can you please send me the offending .s file
> (`make arch/mips/mm/sc-ip22.s') and the GAS invocation line used? GCC
> will print the latter along all kinds of diagnostic stuff if -v is passed
> to an invocation involving assembly (e.g. `make V=1 CFLAGS_sc-ip22.o=-v
> arch/mips/mm/sc-ip22.o'). You can send me the whole diagnostics, I'll
> filter what I need.
>
> I think it'll be the most efficient way to move forward; otherwise I may
> keep missing the issue.
I extracted a rather simple test case:
$ echo >> testcase .s << EOF
.set mips3
dli $2, 0x9000000080000000
EOF
$ mips-linux-as -mips3 -march=r4600 -o testcase.o testcase.s
testcase.s: Assembler messages:
testcase.s:2: Error: number (0x9000000080000000) larger than 32 bits
$ mips-linux-as -mips4 -march=vr5000 -o testcase.o testcase.s
$
I can trigger the error message with vanilla 2.25 and 2.26 but not 2.24.
Ralf
next prev parent reply other threads:[~2016-04-18 15:54 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
2016-04-18 13:34 ` Ralf Baechle
2016-04-18 14:25 ` Maciej W. Rozycki
2016-04-18 15:54 ` Ralf Baechle [this message]
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=20160418155440.GC24051@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@imgtec.com \
--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