From: Ralf Baechle <ralf@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: arch/mips/sgi-ip22/Platform:29: *** gcc doesn't support needed option -mr10k-cache-barrier=store. Stop.
Date: Thu, 10 Apr 2014 02:38:06 +0200 [thread overview]
Message-ID: <20140410003806.GV17197@linux-mips.org> (raw)
In-Reply-To: <5345DB6A.7060004@gentoo.org>
On Wed, Apr 09, 2014 at 07:44:42PM -0400, Joshua Kinard wrote:
> > I notice there is also a mips64 compiler. Should I use that?
The difference between a mips-linux, mips64-linux, mips64el-linux or mipsel-linux
compiler are only the defaults and they can be overridden with command
line options; the kernel makefiles will pass the required options.
> If you weren't using a mips64 compiler, that's probably the issue. R10000
> processors are 64-bit only, so a 'mips' toolchain probably doesn't include
> the R10K cache-barrier code, causing that option to fail.
No - there's no mode switch. An R10000 will happily run 32-bit code
otherwise 32 bit kernels wouldn't work. 32 bit code just doesn't use
64 bit addressing, instructions or the upper 32 bit of the 64 bit registers.
$ mips-linux-gcc -mr10k-cache-barrier=store -c -O2 -o c.o c.c
c.c:1:0: error: ‘-mr10k-cache-barrier’ requires a target that provides the ‘cache’ instruction
[...]
When adding an option like -mips32 the compilation will succeed.
> Are you configuring for IP22 (Indy, Indigo2 R4x00), or IP28 (R10000)? Note,
> IP26 (R8000) is not supported in Linux. I think OpenBSD got it working, though.
Wish I'd have a box ....
Ralf
next prev parent reply other threads:[~2014-04-10 0:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <534138d9.RISUZQYUMS8U8s42%fengguang.wu@intel.com>
2014-04-09 5:19 ` arch/mips/sgi-ip22/Platform:29: *** gcc doesn't support needed option -mr10k-cache-barrier=store. Stop Fengguang Wu
2014-04-09 8:24 ` Florian Lohoff
2014-04-09 13:32 ` Thomas Bogendoerfer
2014-04-09 23:13 ` Fengguang Wu
2014-04-09 23:44 ` Joshua Kinard
2014-04-10 0:38 ` Ralf Baechle [this message]
2014-04-10 3:02 ` Joshua Kinard
2014-04-10 6:59 ` Ralf Baechle
2014-04-13 20:23 ` Joshua Kinard
2014-04-10 12:10 ` Miod Vallat
2014-04-10 12:46 ` Ralf Baechle
2014-04-10 13:21 ` Thomas Bogendoerfer
2014-04-11 1:59 peter fuerst
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=20140410003806.GV17197@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox