From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@linux-mips.org
Subject: Re: Latest sources from CVS.
Date: Thu, 05 Dec 2002 12:14:44 +0100 [thread overview]
Message-ID: <3DEF3524.7A5CDE57@mips.com> (raw)
In-Reply-To: 20021205043444.B29939@linux-mips.org
Ralf Baechle wrote:
> On Wed, Dec 04, 2002 at 10:09:54AM +0100, Kevin D. Kissell wrote:
>
> > For those on the list who don't understand Carsten's sense
> > of humour, I think that was missing a smiley! ;-)
> > I mean, sure, we'd like to move more people toward SDE,
> > but "force" is putting it a bit strongly! And if those directives
> > are really being used unconditionally, I worry that the code
> > being generated is likewise emitting MIPS32 instructions
> > that won't work on the "ghost fleet" of abandoned workstations
> > now running Linux on R4K/R5K CPUs.
>
> A fix is now in CVS. With this fix only compiling a kernel for MIPS32
> and MIPS64 CPUs will require a the new tools.
>
> Everybody satisfied?
Not quite, I afraid.
I would like to be able to compile a 64-bit kernel, using the
MIPS32/MIPS64 config1 register, but I don't have a MIPS64 compliant n64
compiler (assembler). So I need the hardcoded ".word" opcode version, we
previously had.
Something like this:
/*
* This should be changed when we get a compiler that support the MIPS32
ISA.
*/
#define read_mips32_cp0_config1() \
({ int __res; \
__asm__ __volatile__( \
".set\tnoreorder\n\t" \
".set\tnoat\n\t" \
"#.set\tmips64\n\t" \
"#mfc0\t$1, $16, 1\n\t" \
"#.set\tmips0\n\t" \
".word\t0x40018001\n\t" \
"move\t%0,$1\n\t" \
".set\tat\n\t" \
".set\treorder" \
:"=r" (__res)); \
__res;})
>
> I was quite amazed how much email in just like 2 days this change was
> producing, even people binutils 2.8 started yelling ...
>
> Ralf
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-12-05 11:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:34 Latest sources from CVS Carsten Langgaard
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 13:04 ` Ralf Baechle
2002-12-05 3:34 ` Ralf Baechle
2002-12-05 11:14 ` Carsten Langgaard [this message]
2002-12-05 13:47 ` Maciej W. Rozycki
2002-12-05 14:12 ` Carsten Langgaard
2002-12-05 14:27 ` Ralf Baechle
2002-12-06 12:52 ` Carsten Langgaard
2002-12-06 13:07 ` Ralf Baechle
2002-12-06 13:24 ` Carsten Langgaard
2002-12-06 13:24 ` Thiemo Seufer
2002-12-06 13:34 ` Thiemo Seufer
2002-12-06 13:41 ` Carsten Langgaard
2002-12-06 13:51 ` Thiemo Seufer
2002-12-06 16:32 ` Maciej W. Rozycki
2002-12-06 16:45 ` Thiemo Seufer
2002-12-06 17:01 ` Maciej W. Rozycki
2002-12-06 17:24 ` Thiemo Seufer
2002-12-06 18:04 ` Ralf Baechle
2002-12-06 18:30 ` Maciej W. Rozycki
2002-12-06 18:41 ` Thiemo Seufer
2002-12-06 18:58 ` Maciej W. Rozycki
2002-12-06 17:02 ` Ralf Baechle
2002-12-06 17:15 ` Thiemo Seufer
2002-12-06 17:34 ` Greg Lindahl
2002-12-06 18:18 ` Dominic Sweetman
2002-12-06 18:40 ` Greg Lindahl
2002-12-06 23:17 ` Ralf Baechle
2002-12-06 23:33 ` Thiemo Seufer
2002-12-07 0:00 ` Ralf Baechle
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=3DEF3524.7A5CDE57@mips.com \
--to=carstenl@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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.