From: David Edelsohn <dje@watson.ibm.com>
To: James E Wilson <wilson@specifixinc.com>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Subject: Re: generic vectors: how should they work?
Date: Wed, 01 Sep 2004 20:40:00 -0000 [thread overview]
Message-ID: <200409012040.i81KecO30194@makai.watson.ibm.com> (raw)
In-Reply-To: Message from James E Wilson <wilson@specifixinc.com> of "Wed, 01 Sep 2004 13:12:12 PDT." <41362D1C.2020906@specifixinc.com>
>>>>> James E Wilson writes:
James> I think the biggest hole is the lack of an operator to extract an
James> element from a vector. If you want target independent code to extract
James> an element from a vector, then you have to use a union. However, once
James> you use a union, you no longer have vector operations, and can't use the
James> hardware vector instructions. Instead, what happens is that the vector
James> gets forced into a stack slot so we can index into it. Maybe we could
James> reuse the array syntax for this, e.g vector[0] to extract the first
James> element of the vector?
Honza submitted a patch to implement additional init/set/extract
expanders, but the second patch never was reviewed.
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00050.html
David
next prev parent reply other threads:[~2004-09-01 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 0:35 Janis Johnson
2004-09-01 2:11 ` David Edelsohn
2004-09-01 7:11 ` Paolo Bonzini
2004-09-01 14:49 ` David Edelsohn
2004-09-01 15:13 ` Paolo Bonzini
2004-09-01 15:35 ` Giovanni Bajo
2004-09-01 16:00 ` Paolo Bonzini
2004-09-01 19:52 ` Richard Henderson
2004-09-01 22:08 ` David Edelsohn
2004-09-02 13:04 ` Paolo Bonzini
2004-09-02 14:06 ` David Edelsohn
2004-09-02 14:27 ` Paolo Bonzini
2004-09-02 18:33 ` Janis Johnson
2004-09-01 23:47 ` Janis Johnson
2004-09-02 17:46 ` Janis Johnson
2004-09-01 20:12 ` James E Wilson
2004-09-01 20:40 ` David Edelsohn [this message]
2004-09-01 21:22 ` James E Wilson
2004-09-02 1:07 ` Richard Henderson
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=200409012040.i81KecO30194@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=wilson@specifixinc.com \
/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).