linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Holger Bettag <hobold@Informatik.Uni-Bremen.DE>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: altivec
Date: 09 Jul 1999 14:14:49 +0200	[thread overview]
Message-ID: <8x673uf29y.fsf@s53.informatik.uni-bremen.de> (raw)
In-Reply-To: Sacha Varma's message of Fri, 09 Jul 1999 12:29:35 +0100


Sacha Varma <sacha@ssl.co.uk> writes:

> 
> Some questions about altivec & LinuxPPC:
> 
> 1. is there a free C compiler supporting altivec instructions for
>    linuxPPC?
>
Possibly. Someone from Cygnus (the maintainers of egcs/gcc) mentioned he'd
gotten source patches from Motorola that add AltiVec support to gcc.

Since MacOS X is a descendant of NeXTStep, and since NeXT always used gcc,
and since Apple is going to embrace AltiVec, one can reasonably expect that
at least Apple will use an AltiVec-aware variant of gcc. In an ideal world,
AltiVec support would make it into the main gcc tree.

> 2. would it be possible to trap altivec instructions on a non-altivec
>    processor and reroute them through code using generic instructions?

Possible - yes. Dead slow - absolutely. (Apple's simulator is strictly a
development tool, nothing more.)

>    (I believe this is how Apple's MacOS altivec simulator does it).

I don't know.

>    Presumably there is a bad instruction interrupt or something and
>    code in the kernel to trap these interrupts? (Excuse my naivety;
>    I'm more of a kernel user than hacker - for now!)
>
Yes, such exceptions are supported by PPC hardware.

> 3. has anyone written a C library to simulate the altivec instructions?
>
Apple's simulator is the only such program I know of.

  Holger

[[ 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-09 12:14 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 ` Holger Bettag [this message]
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
  -- 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=8x673uf29y.fsf@s53.informatik.uni-bremen.de \
    --to=hobold@informatik.uni-bremen.de \
    --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).