Anton,
Clang was generating an error on vector initializers, when all the vector slots are not provided, i.e.:
vector unsigned int v = (vector unsigned int)(vector int)(-1);
Instead of:
vector unsigned int v = (vector unsigned int)(vector int)(-1, -1, -1, -1);
I’m seeing these kinds of statements in some headers in the PS3 sdk, which gcc allows.
I’ve checked in a fix and revised the altivec tests. (Sorry I missed a test last night, and broke the build.)
I have a question, though (for Anton or anyone). What will the initializers be for the unspecified slots? Will they be 0? What does gcc do?
-John