search for: cunzip

...floating-point type from the imaginary portions >> of a vector of complex (not all variants shown) >> >> declare v4f32 @llvm.extractimag.v4c32(v4c32 %val) declare v4f64 >> @llvm.extractimag.v4c64(v4c64 %val) > > I think that "cunzip" returning a pair of vectors would be better. If > both results are needed, they could usually be generated by a single > instruction corresponding to some kind of a shuffle, but in order to > generate that instruction, the backend would have to see both of the > "extract*&qu...

All, Here is the second revision of the proposal for a complex type in LLVM. It clarifies a few things that came up during discussion and adds additional operations for complex types. -David Proposal to Support Complex Operations in LLVM ---------------------------------------------- Revision History v1 - Initial proposal [1] v2 - This proposal - Added complex of

Ahead of the Wednesday’s roundtable at the developers’ conference, here is version three of the proposal for first-class complex types in LLVM. I was not able to add Krzysztof Parzyszek’s suggestion of a “cunzip” intrinsic returning two vectors as I could not find examples of intrinsics that return two values at the IR level. The Hexagon intrinsics declared to return two values do not actually have both of their values used at the IR level as far as I can determine. We can discuss this more at the roundt...

...34, David Greene via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Ahead of the Wednesday’s roundtable at the developers’ conference, here is version three of > the proposal for first-class complex types in LLVM. I was not able to add Krzysztof Parzyszek’s > suggestion of a “cunzip” intrinsic returning two vectors as I could not find examples of intrinsics > that return two values at the IR level. The Hexagon intrinsics declared to return two values do > not actually have both of their values used at the IR level as far as I can determine. We can > discuss this mor...