From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Dominic Sweetman <dom@mips.com>,
Eric Christopher <echristo@redhat.com>,
Long Li <long21st@yahoo.com>,
Linux/MIPS Development <linux-mips@linux-mips.org>,
David Ung <davidu@mips.com>, Nigel Stephens <nigel@mips.com>
Subject: Re: gcc support of mips32 release 2
Date: 24 Mar 2004 13:38:27 +0100 [thread overview]
Message-ID: <87isguwhbw.fsf@mrvn.homelinux.org> (raw)
In-Reply-To: <20040319125502.GA32363@linux-mips.org>
Ralf Baechle <ralf@linux-mips.org> writes:
> On Fri, Mar 19, 2004 at 11:42:11AM +0100, Geert Uytterhoeven wrote:
>
> > > Take a look at the 68020 to see where instruction set madness can lead:
> > >
> > > movel ([42, a0, d0.2*2],123), ([43, a0, d0.2*2], 22)
> > > bfextu ([42, a0, d0.2*2],123){8:8}, d2
> >
> > These instructions didn't complete in 1 cycle, while the new RISCies do.
>
> That's the point, they went overboard with their C^2ISC philosophy. These
> instructions were more or less unusable by compilers of the time and the
> given the rarity were not the most performant instructions of the
> architecture either, so made sense only relativly rarely. So in the end
> the didn't get it right in the beginning which lead to the removal of the
> instruction in 060, if I recall right.
>
> Ralf
Thats a
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?
MfG
Goswin
next prev parent reply other threads:[~2004-03-24 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 7:55 gcc support of mips32 release 2 Long Li
2004-03-05 9:14 ` Eric Christopher
2004-03-05 10:12 ` Dominic Sweetman
2004-03-05 10:12 ` Dominic Sweetman
2004-03-05 17:03 ` Long Li
2004-03-08 11:11 ` Dominic Sweetman
2004-03-08 12:15 ` David Ung
2004-03-08 17:45 ` Eric Christopher
2004-03-18 13:18 ` Maciej W. Rozycki
2004-03-18 14:10 ` Dominic Sweetman
2004-03-18 21:19 ` Ralf Baechle
2004-03-19 13:44 ` Maciej W. Rozycki
2004-03-22 9:42 ` Dominic Sweetman
2004-03-22 11:14 ` Maciej W. Rozycki
2004-03-22 14:49 ` Dominic Sweetman
2004-03-22 16:19 ` Michael Uhler
2004-03-18 16:52 ` Michael Uhler
2004-03-18 21:37 ` Ralf Baechle
2004-03-19 10:42 ` Geert Uytterhoeven
2004-03-19 12:55 ` Ralf Baechle
2004-03-24 12:38 ` Goswin von Brederlow [this message]
2004-03-24 13:52 ` Ralf Baechle
2004-03-24 17:57 ` Dominic Sweetman
2004-03-19 13:47 ` 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=87isguwhbw.fsf@mrvn.homelinux.org \
--to=brederlo@informatik.uni-tuebingen.de \
--cc=davidu@mips.com \
--cc=dom@mips.com \
--cc=echristo@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.com \
--cc=macro@ds2.pg.gda.pl \
--cc=nigel@mips.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox