From: David Edelsohn <dje@watson.ibm.com>
To: Stephane GEORGES <sg@dalim.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: What about AltiVec and egcs ?
Date: Wed, 02 Feb 2000 13:56:19 -0500 [thread overview]
Message-ID: <200002021856.NAA21742@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Stephane GEORGES <sg@dalim.de> of "Wed, 02 Feb 2000 19:40:20 +0100." <38987A14.D5547407@dalim.de>
>>>>> Stephane GEORGES writes:
Stephane> Does anybody knoes if AltiVec will be supported in gcc?
AltiVec is supported in GCC by some patches developed by Motorola
and Apple. I have no idea when those patches will be contributed to and
integrated into the official FSF sources for GCC.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-02-02 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CB9D49DF48337FC1C1256879006153EB.00615423C1256879@kehl.dalim.de>
2000-02-02 18:40 ` What about AltiVec and egcs ? Stephane GEORGES
2000-02-02 18:56 ` David Edelsohn [this message]
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=200002021856.NAA21742@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sg@dalim.de \
/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).