From: Sacha Varma <sacha@ssl.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: altivec
Date: Fri, 10 Sep 1999 11:32:36 +0100 [thread overview]
Message-ID: <37D8DE44.9AE2C717@ssl.co.uk> (raw)
Has any progress been made on LinuxPPC Altivec support? I posted a while back
and there was some discussion, I wondered if anyone was taking it further. I
suppose the arrival of G4 Macs in a few weeks' time will help kickstart things.
It would be great if AIM took the lead in this sort of work...
The issues as I remember them:
.. saving/restoring altivec registers (there's sample machine
code for one of the ABIs in the Altivec documentation)
.. support in egcs for the Altivec C language extensions,
hopefully C++ also (someone said they had patches supplied
by Motorola, but I've not found mention of these on the
Motorola SPS site so I assume they're not for general
consumption)
There was some talk of trapping an illegal instruction interrupt in
Altivec-compiled code on non-Altivec processors and then emulating it in
software, but as I recall this was thought to be maybe impossible (due to
limited information about the illegal instruction and limits on what you can do
in the trap) or more effort than it's worth.
In the meantime to learn more about Altivec I've been working on a library to
emulate the instructions in software (with appropriate #defines for the language
extensions in a header). If anyone's interested e-mail me and I'll let you know
if/when I'm done; I'm hoping to get the bulk of it done this weekend. (It'll be
C++ I'm afraid - the vector types lend themselves nicely to a template class,
and a lot of the vec_* instructions are overloaded).
--
sacha varma : system simulation ltd : sacha@ssl.co.uk
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-10 10:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 10:32 Sacha Varma [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-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 ` altivec Mike DeSimone
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
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=37D8DE44.9AE2C717@ssl.co.uk \
--to=sacha@ssl.co.uk \
--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).