From: Mike Stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, kumar@chaos.ph.utexas.edu
Subject: Re: AltiVec support in GCC
Date: Fri, 18 Feb 2000 17:13:00 -0000 [thread overview]
Message-ID: <200002190112.RAA17849@kankakee.wrs.com> (raw)
> Date: Thu, 17 Feb 2000 22:30:00 -0600 (CST)
> From: Kumar Gala <kumar@chaos.ph.utexas.edu>
> To: gcc@gcc.gnu.org
> The major issues that I have been told about, surrounds the fact that the
> Motorola changes add a 'vector' primitive.
Sounds half way reasonable. I have here in my hand a piece of paper,
no, a compiler for the Pentium III SSE with intrinsic support for SSE.
It adds a vector type to the compiler also.
Would be nice if a person in the know took the moto patches and the
SSE patches and unified them... If not, then the first set in, wins,
and the other will just have to cope, extend and transform.
> the C API is much more like 'c' function calls
Same with the SSE stuff.
> Also, people have discussed the creation of auto-vectorizing
> compilers. While this can be useful for the simple case, from the
> AltiVec code I think it would be very diffucult to get full use of
> the AltiVec instruction set.
Yes, this is a longer range goal that shouldn't be worried about at
first. I think we can postpone talks about it.
next reply other threads:[~2000-02-18 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-18 17:13 Mike Stump [this message]
2000-02-18 18:04 ` Stan Shebs
2000-02-20 10:56 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 10:10 altivec support in gcc Michel LESPINASSE
2003-04-09 16:57 ` Aldy Hernandez
2003-04-09 22:55 ` Michel LESPINASSE
2000-02-18 18:47 AltiVec support in GCC Mike Stump
2000-02-19 15:03 ` Geoff Keating
2000-02-17 20:30 Kumar Gala
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=200002190112.RAA17849@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=gcc@gcc.gnu.org \
--cc=kumar@chaos.ph.utexas.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).