[Top] [All Lists]

Re: gcc support of mips32 release 2

To: Goswin von Brederlow <>
Subject: Re: gcc support of mips32 release 2
From: Ralf Baechle <>
Date: Wed, 24 Mar 2004 14:52:25 +0100
Cc: Geert Uytterhoeven <>, "Maciej W. Rozycki" <>, Dominic Sweetman <>, Eric Christopher <>, Long Li <>, Linux/MIPS Development <>, David Ung <>, Nigel Stephens <>
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <> <> <>
User-agent: Mutt/1.4.1i
On Wed, Mar 24, 2004 at 01:38:27PM +0100, Goswin von Brederlow wrote:

>  move.l 31530(A0, D0*2), 5675(A0, D0*2)  (that would give a bus error)
> before assembly right?
> That instruction is great to access array or aligned structure members
> with an offset and compilers should be able to generate it for it. But
> its only realy usefull if your short on registers, which gcc does not
> optimize for.
> Don't think they got removed. Could it be you are thinking about
> mulu.l d0,d0:d1   (32*32=64 bit mul) and the like?

Maybe - my memories of 68k are getting dusty.  In '92 or '93 I had started
my own Linux/68k port but disgusted by the complexity of some parts of the
68k architecture - such as execution timing tables of several pages just
for the move instruction or even shell scripts in case of the 68851 MMU.
Eventually I got my hands on a MIPS box in '94, again for porting Linux
to MIPS as the very first MIPS project I ever did.  Architectures tend to
get ugly when they age, when new features are added and compatibility
issues arrise but for most part I think MIPS has managed to age very
gracefully which I believe in part is one of the benefits of RISC design
principles, so I'm still happy after 10 years of MIPS stuff and feel
little desire to open those Motorola manuals on my shelf :-)


<Prev in Thread] Current Thread [Next in Thread>