From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Big Endian broken?
Date: Tue, 3 Jun 2014 11:32:42 +0100 [thread overview]
Message-ID: <20140603103242.GF933@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5340132.TxQQqdITJ3@wuerfel>
On Tue, Jun 03, 2014 at 12:13:37PM +0200, Arnd Bergmann wrote:
> On Tuesday 03 June 2014 10:56:19 Russell King - ARM Linux wrote:
> > Last night's randconfig build had big endian enabled:
> >
> > CONFIG_CPU_BIG_ENDIAN=y
> > CONFIG_CPU_ENDIAN_BE8=y
> >
> > which found this:
> >
> > CC lib/lockref.o
> > /tmp/ccWo86hf.s: Assembler messages:
> > /tmp/ccWo86hf.s:63: Error: even register required -- `strexd r1,r5,r6,[r4]'
> > /tmp/ccWo86hf.s:135: Error: even register required -- `strexd r1,r5,r6,[r4]'
> > /tmp/ccWo86hf.s:212: Error: even register required -- `strexd r1,r5,r6,[r4]'
> > /tmp/ccWo86hf.s:291: Error: even register required -- `strexd r1,r5,r6,[r4]'
> > /tmp/ccWo86hf.s:398: Error: even register required -- `strexd r1,r5,r6,[r4]'
> > make[2]: *** [lib/lockref.o] Error 1
> >
> > It looks to me like a toolchain issue - the compiler has swapped the
> > register order from (r6,r5) to (r5,r6) for BE, but the assembler still
> > wants (<even>,<odd>) for this instruction. Maybe the BE guys can take
> > a look?
> >
> > Full config:
> >
> > http://www.arm.linux.org.uk/developer/build/file.php?lid=8653
> >
>
>
> Which toolchain are you using? I just tried reproducing this but
> it works on linux-next with your config for every version I tried:
> ubuntu 4.6, 4.7, 4.8 and vanilla 4.8.0, 4.8.3, 4.9.0, 4.10-pre,
> and gas 2.23.52.20130913 as well as 2.24.51.20131021.
stock gcc 4.6.4 with stock binutils 2.22.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
prev parent reply other threads:[~2014-06-03 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 9:56 Big Endian broken? Russell King - ARM Linux
2014-06-03 10:13 ` Arnd Bergmann
2014-06-03 10:32 ` Russell King - ARM Linux [this message]
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=20140603103242.GF933@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).