This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How is generic SIMD support supposed to work?
- From: Richard Henderson <rth at redhat dot com>
- To: Jan Hubicka <jh at suse dot cz>
- Cc: gcc at gcc dot gnu dot org, shebs at apple dot com, aldyh at redhat dot com, aj at suse dot de, rakdver at atrey dot karlin dot mff dot cuni dot cz
- Date: Sun, 20 Oct 2002 11:42:19 -0700
- Subject: Re: How is generic SIMD support supposed to work?
- References: <20021020124628.GD25286@kam.mff.cuni.cz>
On Sun, Oct 20, 2002 at 02:46:28PM +0200, Jan Hubicka wrote:
> __v4si val = {1,2,3,4};
> return val;
> }
> and I hope this to be compiled into static initializer loaded at once.
> Unforutnately this does not happen, but even worse compiler dies:
What happens on other architectures is that this value gets
loaded into 4 integer registers, and the subregging works as
expected. That's going to be prohibitive on x86, so we either
need to arrange for such pseudos to get allocated to the stack
(via CLASS_CANNOT_CHANGE_MODE_P), and/or come up with another
mechanism (via named patterns, I assume) for the code generator
to ask to read or set a vector element.
r~