search for: strunc

...pattern, and scalarize the general > case as necessary. I have a rough draft of a patch for this that works reasonably well for simple cases... I don't think I really have the time to finish it properly, but I'll clean it up a bit and send it to you as a starting point. > 2) Vector strunc, sext, zext, fptrunc and fpext > > Again, I think these are hopefully straightforward. Please let me know > if you expect any issues with vector operations that change element > sizes from the RHS to the LHS, e.g. around legalization. These are tricky to generate efficient code for bec...

...the shifting instructions to naturally apply to vectors as well. One issue is that these operations often only support a single shift amount for an entire vector. I assume it should be fairly straightforward to select on this pattern, and scalarize the general case as necessary. 2) Vector strunc, sext, zext, fptrunc and fpext Again, I think these are hopefully straightforward. Please let me know if you expect any issues with vector operations that change element sizes from the RHS to the LHS, e.g. around legalization. 3) Vector intrinsics for floor, ceil, round, frac/modf These are...

...le shift > amount for an entire vector. I assume it should be fairly So you're assuming a shift of a vector by a scalar? What about the general vector-by-vector version? > straightforward to select on this pattern, and scalarize the general > case as necessary. Yep. > 2) Vector strunc, sext, zext, fptrunc and fpext > > Again, I think these are hopefully straightforward. Please let me know > if you expect any issues with vector operations that change element > sizes from the RHS to the LHS, e.g. around legalization. Is the assumption that all elements are changed in...

...ng a shift of a vector by a scalar? What about the > general vector-by-vector version? No, I am proposing a general vector-by-vector version, just pointing out that many architectures do not support this natively, but that this should be a simple matter of legalization. >> 2) Vector strunc, sext, zext, fptrunc and fpext >> >> Again, I think these are hopefully straightforward. Please let me >> know >> if you expect any issues with vector operations that change element >> sizes from the RHS to the LHS, e.g. around legalization. > > Is the assumpti...

...nably well > for simple cases... I don't think I really have the time to finish it > properly, but I'll clean it up a bit and send it to you as a starting > point. That's great. Please do send it over, it'd be great to have a starting point like this. >> 2) Vector strunc, sext, zext, fptrunc and fpext >> > These are tricky to generate efficient code for because they change > the size of the vector and most likely introduce illegal vectors. > It'll be a lot of work to get these working well for non-trivial > cases. Right, though it seems they...

...pply to vectors as well. > One issue is that these operations often only support a single shift > amount for an entire vector. I assume it should be fairly > straightforward to select on this pattern, and scalarize the general > case as necessary. That seems reasonable. > 2) Vector strunc, sext, zext, fptrunc and fpext > > Again, I think these are hopefully straightforward. Please let me know > if you expect any issues with vector operations that change element > sizes from the RHS to the LHS, e.g. around legalization. Is the proposed semantics here that the number of e...