This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: new rtl vec_set_unit/vec_get_unit
- From: Jan Hubicka <jh at suse dot cz>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: GCC Mailinglist <gcc at gcc dot gnu dot org>, Jan Hubicka <jh at suse dot cz>,Richard Henderson <rth at redhat dot com>
- Date: Fri, 28 Mar 2003 00:21:40 +0100
- Subject: Re: RFC: new rtl vec_set_unit/vec_get_unit
- References: <80BD18BC-6099-11D7-BCCF-000393750C1E@redhat.com>
> I can't seem to find the original thread on the GCC archive, but...
> there was a discussion a while back between Jan, Richard, and me about
> subregs of SIMD types creating bogus code.
>
> Particularly, when we have a hard register, both of the following
> snippets end up referencing r0 because we have no way of distinguishing
> the upper and the lower halves:
>
> (set (subreg:SI (reg:V2SI r0) 0) (reg:SI xx))
> (set (subreg:SI (reg:V2SI r0) 4) (reg:SI xx))
>
> It was suggested that we add new RTL code to deal with this, but the
> exact semantics had not been proposed. I'm taking this up again, and
> here is the proposed syntax:
>
> (vec_set_unit:SI (reg:V2SI r9) 1 (reg:SI r5))
>
> and
>
> (set (reg:SI r88) (vec_get_unit:SI (reg:V2SI r9) 1))
>
> Then, the expanders:
>
> (define_expand "vec_set_unitv2si"
> (set (match_operand:V2SI 0)
> (vec_set_unit:V2SI (match_operand:V2SI 1)
> (match_operand 2 immediate)
> (match_operand:SI 3)))
>
> and...
>
> (define_expand "vec_get_unitv2si"
> [(set (match_operand:SI 0)
> (vec_get_unit:SI (match_operand:V2SI 1)
> (match_operand:SI 2)))]
>
> I think it's all pretty clear. If no one objects as to the syntax,
> I'll start hacking away.
This is still something I would like to look into. The expanders to
get/set pariticular fields of the vector looks like obvious sollution.
However the problem is that the code generated for SSE would be ugly,
especially when taking into account V16QImode where to access paritcular
mode number of rotations on different temporaries needs to be made.
Most of the time we need to get/set all the fields of vector at once (to
simulate vector operation) so perhaps we should have both.
We probably need both mechanizms as in some cases it is deifnitly
desirable to access particular fields of the vector.
Also vec_set_unit/vec_get_unit can be expanded into
vec_select/vec_duplicate operations so there is probably no need to
invent the RTL construct for that, we only need the named patterns.
Honza
>
> Aldy