This is the mail archive of the
mailing list for the GCC project.
Re: A Far Less Ambitous AltiVec patch
But this is insufficient for AltiVec, where more than one AltiVec type
can map to the
same generic vector layout. For example, the types 'vector unsigned
short', 'vector bool short'
and 'vector pixel' all are implemented as a vector holding 8 unsigned
That's a bug, then, and should be fixed.
It's fine for these vectors to have the same machine mode, just as int
and long often have the same machine mode. But, just as int and long
have separate types, so should these vectors.
A VECTOR_TYPE has a slot for saying what the element types are. They
should be different in each of the cases you give above. And, the
generic mangling code for VECTOR_TYPEs should just encode the number of
elements and the type of the elements.