From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Florian Lohoff <f@zz.de>, Michal Marek <mmarek@suse.cz>,
kbuild-all@01.org,
"linux-mips@linux-mips.org" <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 15:21:08 +0200 [thread overview]
Message-ID: <20140410132108.GA23466@alpha.franken.de> (raw)
In-Reply-To: <20140409231345.GC8370@localhost>
On Thu, Apr 10, 2014 at 07:13:45AM +0800, Fengguang Wu wrote:
> > Iirc it went into 4.4.0.
>
> That's interesting. I'm using the cross compiler
>
> gcc-4.6.3-nolibc/mips-linux
well the feature went into the gcc codebase 2008 according to ChangeLog-2008.
The mips64 cross compiler from FC19 (4.7.2) supports r10k-cache-barriers
out of the box.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2014-04-10 13:21 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
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 [this message]
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=20140410132108.GA23466@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=f@zz.de \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mips@linux-mips.org \
--cc=mmarek@suse.cz \
/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.