All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Sacha Varma <sacha@ssl.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: altivec
Date: Fri, 10 Sep 1999 13:59:35 +0200	[thread overview]
Message-ID: <19990910135935.015493@mailhost.mipsys.com> (raw)
In-Reply-To: <37D8DE44.9AE2C717@ssl.co.uk>


On Fri, Sep 10, 1999, Sacha Varma <sacha@ssl.co.uk> wrote:

>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.

This is possible since Apple provides an emulator for developers (it's an
extension that you drop in your MacOS system folder and which traps the
illegal instruction interrupt).

>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).

If your library can be turned into plain C, then we should be able to
implement the same emulation mecanism in Linux, but is it really
interesting ? It will be way too slow to be useful for anything but
developers prototyping Altivec code on G3s.

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-10 11:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-10 10:32 altivec Sacha Varma
1999-09-10 11:59 ` Benjamin Herrenschmidt [this message]
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=19990910135935.015493@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sacha@ssl.co.uk \
    /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.