Displaying 2 results from an estimated 2 matches for "vuint8_t".
Did you mean:
uint8_t
2009 Nov 10
4
[LLVMdev] Altivec vs the type legalizer
...ll be relying on ConstantVector::get
and getConstantPool to work even with elements of a type that's
illegal for the target; currently, they do. (And I see no other way
to fix it except to break the vector into scalars, which produces
horrendous code.)
typedef vector unsigned char vuint8_t;
vuint8_t baz;
void foo(vuint8_t x) {
vuint8_t temp = (vuint8_t)(22,21,20, 3, 25,24,23, 3, 28,27,26, 3,
31,30,29, 3);
baz = vec_add(x, temp);
}
2009 Nov 10
0
[LLVMdev] Altivec vs the type legalizer
...t
> and getConstantPool to work even with elements of a type that's
> illegal for the target; currently, they do. (And I see no other way
> to fix it except to break the vector into scalars, which produces
> horrendous code.)
>
>
> typedef vector unsigned char vuint8_t;
> vuint8_t baz;
> void foo(vuint8_t x) {
> vuint8_t temp = (vuint8_t)(22,21,20, 3, 25,24,23, 3, 28,27,26, 3,
> 31,30,29, 3);
> baz = vec_add(x, temp);
> }
Earlier this year we ran into a similar problem for NEON and ended up modifying the type rules for BUILD_VECTOR so tha...