From: Ralf Baechle <ralf@oss.sgi.com>
To: Stewart Brodie <stewart.brodie@pace.co.uk>
Cc: linux-mips@oss.sgi.com
Subject: Re: CONFIG_MIPS32 implies CONFIG_CPU_HAS_PREFETCH
Date: Wed, 7 Aug 2002 17:25:31 +0200 [thread overview]
Message-ID: <20020807172531.A16609@dea.linux-mips.net> (raw)
In-Reply-To: <0de052624b.sbrodie@sbrodie.cam.pace.co.uk>; from stewart.brodie@pace.co.uk on Wed, Aug 07, 2002 at 04:04:16PM +0100
On Wed, Aug 07, 2002 at 04:04:16PM +0100, Stewart Brodie wrote:
> linux_2_4 branch question: In config-shared.in, and previously in config.in,
> whether or not the CPU has prefetch instructions seems to be dependent only
> on whether CONFIG_MIPS32 is y. However, this causes our kernel builds to die
> when compiling memcpy.S because the compiler is objecting to the pref/prefx
> instructions. The gcc 2.96 compiler options we are using are -mtune=r4600
> and -mips2.
>
> Is it simply the case that the processors on all the boards supported in the
> MIPS builds all support prefetch? At the moment, I've just put a specific
> check in for our particular processor to stop CONFIG_CPU_HAS_PREFETCH from
> being set to y and that stops the problem. In earlier (2.4.17 pre-release)
> kernels, whether or not to define PREF/PREFX as pref/prefx or the empty
> string was determined on a stricter set of criteria based around actual CPU
> types rather than a blanket check on being a 32-bit MIPS.
The MIPS32 architecture specifies a prefetch instruction. So it's correct
(though not necessarily alway the most efficient thing) to assume your
system has this instruction available. The compiler option -mips2 which
you're specifying however tells the tools that you do not have that
instruction, so is wrong.
Ralf
next prev parent reply other threads:[~2002-08-07 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 15:04 CONFIG_MIPS32 implies CONFIG_CPU_HAS_PREFETCH Stewart Brodie
2002-08-07 15:25 ` Ralf Baechle [this message]
2002-08-07 15:41 ` Maciej W. Rozycki
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=20020807172531.A16609@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=stewart.brodie@pace.co.uk \
/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