From: David Edelsohn <dje@watson.ibm.com>
To: Sacha Varma <sacha@ssl.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: altivec
Date: Fri, 10 Sep 1999 13:39:31 -0400 [thread overview]
Message-ID: <9909101739.AA34034@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Sacha Varma <sacha@ssl.co.uk> of "Fri, 10 Sep 1999 11:32:36 BST." <37D8DE44.9AE2C717@ssl.co.uk>
>>>>> Sacha Varma writes:
Sacha> Has any progress been made on LinuxPPC Altivec support? I posted a while back
Sacha> and there was some discussion, I wondered if anyone was taking it further. I
Sacha> suppose the arrival of G4 Macs in a few weeks' time will help kickstart things.
Sacha> It would be great if AIM took the lead in this sort of work...
Sacha> The issues as I remember them:
Sacha> .. support in egcs for the Altivec C language extensions,
Sacha> hopefully C++ also (someone said they had patches supplied
Sacha> by Motorola, but I've not found mention of these on the
Sacha> Motorola SPS site so I assume they're not for general
Sacha> consumption)
Apple apparently has a version of egcs-1.1.2 with an improved
version of Motorola's AltiVec support merged in. I still have not seen
any offer of these patches to the GCC maintainers (and accompanying
assignment to the FSF) for inclusion in the public sources.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-10 17:39 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 ` 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 ` David Edelsohn [this message]
-- 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=9909101739.AA34034@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--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 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).