search for: 3xf32

...that I necessarily think they should be, it's just a nice side effect). If this is feasible, it would be nice to extend it all the way. This lets you do things like: float3 x; float4 y; // ... y.xyz = x; as a single shufflevector, e.g.: %y2 = shufflevector <4xf32> %y1, <3xf32> %x, <4, 5, 6, 3> I assume my proposed generalization can't hurt codegen, since it could always be turned into a sequence of insert and extracts which would provide the same behaviour as today. -- Stefanus Du Toit <stefanus.dutoit at rapidmind.com> RapidMind Inc. phon...

...nice side effect). > > If this is feasible, it would be nice to extend it all the way. This > lets you do things like: > > float3 x; > float4 y; > > // ... > > y.xyz = x; > > as a single shufflevector, e.g.: > > %y2 = shufflevector <4xf32> %y1, <3xf32> %x, <4, 5, 6, 3> > > I assume my proposed generalization can't hurt codegen, since it could > always be turned into a sequence of insert and extracts which would > provide the same behaviour as today. > > -- > Stefanus Du Toit <stefanus.dutoit at rapidmind.com&...

...le, it would be nice to extend it all the way. This >> lets you do things like: >> >> float3 x; >> float4 y; >> >> // ... >> >> y.xyz = x; >> >> as a single shufflevector, e.g.: >> >> %y2 = shufflevector <4xf32> %y1, <3xf32> %x, <4, 5, 6, 3> >> >> I assume my proposed generalization can't hurt codegen, since it >> could >> always be turned into a sequence of insert and extracts which would >> provide the same behaviour as today. >> >> -- >> Stefanus Du Toi...

Hi, The current definition of shuffle vector is <result> = shufflevector <n x <ty>> <v1>, <n x <ty>> <v2>, <n x i32> <mask> ; yields <n x <ty>> The first two operands of a 'shufflevector' instruction are vectors with types that match each other and types that match the result of the instruction. The third