Displaying 3 results from an estimated 3 matches for "bvec4".
Did you mean:
bvec
2007 Apr 24
1
[LLVMdev] Instruction pattern type inference problem
...This also allows stuff like letting 'select' accept a vector
> boolean predicate and vector values to perform a vector select.
this is the semantics that GLSL uses for vector compares, for example the signature of one of the overloads for the
built-in function 'lessThan' is:
bvec4 lessThan(vec4 x, vec4 y)
what I wanted to mention are the built-in functions 'any' and 'all' which have signatures (for 4-vectors)
bool any(bvec4 x)
bool all(bvec4 x)
and the obvious semantics any(x)= x.x || x.y || x.z || x.w and all(x)= x.x && x.y && x.z &&am...
2007 Apr 23
0
[LLVMdev] Instruction pattern type inference problem
On Apr 23, 2007, at 5:08 PM, Chris Lattner wrote:
> On Sun, 22 Apr 2007, Christopher Lamb wrote:
>> 1. Is there a good reason that v2f32 types are excluded from the
>> isFloatingPoint filter? Looks like a bug to me.
>>
>> v2f32 = 22, // 2 x f32
>> v4f32 = 23, // 4 x f32 <== start ??
>> v2f64 = 24, // 2 x
2007 Apr 23
3
[LLVMdev] Instruction pattern type inference problem
On Sun, 22 Apr 2007, Christopher Lamb wrote:
> 1. Is there a good reason that v2f32 types are excluded from the
> isFloatingPoint filter? Looks like a bug to me.
>
> v2f32 = 22, // 2 x f32
> v4f32 = 23, // 4 x f32 <== start ??
> v2f64 = 24, // 2 x f64 <== end
>
> static inline bool isFloatingPoint(ValueType VT) {