From: Ralf Baechle <ralf@linux-mips.org>
To: Dominic Sweetman <dom@mips.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Eric Christopher <echristo@redhat.com>,
Long Li <long21st@yahoo.com>,
linux-mips@linux-mips.org, David Ung <davidu@mips.com>,
Nigel Stephens <nigel@mips.com>
Subject: Re: gcc support of mips32 release 2
Date: Thu, 18 Mar 2004 22:19:10 +0100 [thread overview]
Message-ID: <20040318211910.GB25815@linux-mips.org> (raw)
In-Reply-To: <16473.44507.935886.271157@arsenal.mips.com>
On Thu, Mar 18, 2004 at 02:10:35PM +0000, Dominic Sweetman wrote:
> Of course, instructions still have to be *useful* to be added.
> Insert/extract make a reasonable case for themselves, but actually
> arrived in MIPS32 release 2 as part of a bunch of other bit-shuffle
> instructions (also includes rotates and various byte-swaps) which -
> together - help quite a bit to manipulate sub-word data in registers.
And in some case where MIPS such as certain crypto algorithms where MIPS
and RISCs used to look rather pale the new instructions will help
significantly.
Ralf
next prev parent reply other threads:[~2004-03-18 21:19 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 [this message]
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
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=20040318211910.GB25815@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davidu@mips.com \
--cc=dom@mips.com \
--cc=echristo@redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.com \
--cc=macro@ds2.pg.gda.pl \
--cc=nigel@mips.com \
/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.