From: Ira Rosen <ira.rosen@linaro.org>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: Fw: RFC: Representing vector lane load/store operations
Date: Wed, 23 Mar 2011 10:02:00 -0000 [thread overview]
Message-ID: <AANLkTinBjMpNN3DPrg81C0f0+_TreVbTejkmpHby35my@mail.gmail.com> (raw)
In-Reply-To: <OF630F8944.96ACEF66-ONC225785C.00363150-C225785C.003637B4@il.ibm.com>
>> ...Ira would know best, but I don't think it would be used for this
>> kind of loop. It would be more something like:
>>
>> for (i=0; i<N; ++i)
>> X[i] = Y[i].red + Y[i].blue + Y[i].green;
>>
>> (not a realistic example). You'd then have:
>>
>> compoundY = __builtin_load_lanes (Y);
>> red = ARRAY_REF <compoundY, 0>
>> green = ARRAY_REF <compoundY, 1>
>> blue = ARRAY_REF <compoundY, 2>
>> D1 = red + green
>> D2 = D1 + blue
>> MEM_REF <X> = D2;
>>
>> My understanding is that'd we never do any operations besides ARRAY_REFs
>> on the compound value, and that the individual vectors would be treated
>> pretty much like any other.
>
> Ok, I thought it might be used to have a larger vectorization factor for
> loads and stores, basically make further unrolling cheaper because you
> don't have to duplicate the loads and stores.
Right, we can do that using vld1/vst1 instructions (full load/store
with N=1) and operate on up to 4 doubleword vectors in parallel. But
at the moment we are concentrating on efficient support of strided
memory accesses.
Ira
parent reply other threads:[~2011-03-23 10:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OF630F8944.96ACEF66-ONC225785C.00363150-C225785C.003637B4@il.ibm.com>]
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=AANLkTinBjMpNN3DPrg81C0f0+_TreVbTejkmpHby35my@mail.gmail.com \
--to=ira.rosen@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=rdsandiford@googlemail.com \
--cc=richard.guenther@gmail.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).