linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike DeSimone <Hot-Wire@mail.utexas.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: altivec
Date: Fri, 9 Jul 1999 19:41:36 -0500	[thread overview]
Message-ID: <v04020a02b3ac45cbc4ab@[192.168.0.2]> (raw)
In-Reply-To: <8xyagpbzxm.fsf@s53.informatik.uni-bremen.de>


>Well, if you do instruction-by-instruction emulation, the iteration count is
>at most 16 (16 bytes in a vector). Furthermore, the overhead of a context
>switch into privileged mode and back again is not negligible (at the very
>least a pipeline flush and some saving/restoring of registers). Finally,
>keeping the emulated vector registers somewhere in memory means that you will
>quite often be limited by the availability of 'only' one load/store unit.

That's true, I forgot about the 16 byte limit.  That will really make the
overhead significant.  Kind of annoying to me (my typical vector length is
over 900).  Maybe having two libraries is the way to go, then...

>> I'm also wondering what has been done on this issue on the Intel side of
>> the fence, since KNI and 3Dnow! are similar to Altivec in concept and, at
>> least for 3Dnow!, implementation.
>>
>Similar? Please forgive my ranting, but AltiVec is feature-complete,
>orthogonal, and implemented without compromises. MMX, 3DNow!, and ISSE have
>none of the above three qualities. They were available sooner, but that's
>about it.

That's why I said "similar in concept" ... not execution.  And I said KNI
(the PIII new instructions), not MMX, which is integers only.  (Also why I
didn't mention Sun's VIS).
_________________________________________________________________________
                                __________
##   ##   ###   #####   #####   \********/   #####    ###    ##### ######
### ###  ## ##  ##  ## ##        \*/\/\*/    ##  ##  ## ##  ##     ##
#######  ## ##  #####   ####       /\/\      #####   ## ##   ####  ####
## # ## ####### ##  ##     ##      \**/      ##  ## #######     ## ##
##   ## ##   ## ##  ## #####        \/       #####  ##   ## #####  ######
_________________________________________________________________________
### Mike DeSimone ### Hot-Wire@mail.utexas.edu ### ares.marsbase.mars ###

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-07-10  0:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-09 11:29 altivec Sacha Varma
1999-07-09 12:14 ` altivec Holger Bettag
1999-07-09 13:04   ` altivec Mike DeSimone
1999-07-09 15:33     ` altivec Holger Bettag
1999-07-10  0:41       ` Mike DeSimone [this message]
1999-07-14 10:17         ` altivec sean o'malley
1999-07-14 21:04           ` altivec Matt Porter
1999-07-14 21:42             ` altivec Josh Huber
  -- strict thread matches above, loose matches on Subject: below --
1999-09-10 10:32 altivec Sacha Varma
1999-09-10 11:59 ` altivec Benjamin Herrenschmidt
1999-09-10 12:27   ` altivec Sacha Varma
1999-09-10 17:43     ` altivec Brad Midgley
1999-09-10 17:51       ` altivec Brad Midgley
1999-09-10 18:02       ` altivec Vitaly Oratovsky
1999-09-10 17:39 ` altivec David Edelsohn
1999-07-20 17:04 altivec David DeHaven
1999-07-20 17:04 altivec David DeHaven
1999-07-20 17:04 altivec David DeHaven
     [not found] <Pine.PMDF.3.96.990715091130.538970498B-100000@uni.edu>
1999-07-15 16:11 ` altivec Matt Porter
1999-07-15 16:22   ` altivec Jason Haas
1999-07-15 16:29     ` altivec Josh Huber
1999-07-15 12:14       ` altivec sean o'malley
1999-07-15 17:36     ` altivec Matt Porter
1999-07-16  6:29   ` altivec Geert Uytterhoeven
1999-07-16 14:47     ` altivec Matt Porter
1999-06-21 14:34 Altivec sean o'malley

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='v04020a02b3ac45cbc4ab@[192.168.0.2]' \
    --to=hot-wire@mail.utexas.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).