From: Joshua Kinard <kumba@gentoo.org>
To: 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: Wed, 09 Apr 2014 19:44:42 -0400 [thread overview]
Message-ID: <5345DB6A.7060004@gentoo.org> (raw)
In-Reply-To: <20140409231345.GC8370@localhost>
On 04/09/2014 19:13, Fengguang Wu wrote:
> On Wed, Apr 09, 2014 at 03:32:29PM +0200, Thomas Bogendoerfer wrote:
>> On Wed, Apr 09, 2014 at 10:24:45AM +0200, Florian Lohoff wrote:
>>> Most likely they never made it into gcc upstream but they are
>>> necessary working around the r10k speculative stores on non
>>> cache coherent machines like the IP28.
>>
>> IMHO the patch went upstream judging from the incremental patches
>> here http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01371.html.
>>
>> Iirc it went into 4.4.0.
>
> That's interesting. I'm using the cross compiler
>
> gcc-4.6.3-nolibc/mips-linux
>
> downloaded from
>
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/
>
> I notice there is also a mips64 compiler. Should I use that?
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.
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.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2014-04-09 23:45 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 [this message]
2014-04-10 0:38 ` Ralf Baechle
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=5345DB6A.7060004@gentoo.org \
--to=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 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.