Displaying 2 results from an estimated 2 matches for "ifavpany".
2015 Jan 16
3
[LLVMdev] Overloaded intrinsics: name explosion
Philip Reames wrote:
>> 1. Introduce aAny.
>
> Having a generic any type seems fine. I assume you'd create something like
> an llvm_any_type in Intrinsics.td?
That's precisely what ifavpAny is about: integer, float, array,
vector, pointer Any. aAny is meant for array-Any, and I wonder why so
few people care about arrays. I'll go ahead with Any and
llvm_any_type.
2015 Jan 15
2
[LLVMdev] Overloaded intrinsics: name explosion
...e suffers from the same problem: we want to be able to
relocate a vector of pointers, but it's simply not possible with its
signature.
My proposal is to:
1. Introduce aAny.
2. Make iAny work with integer arrays (they already work with integer
vectors), fAny work with float arrays.
3. Introduce ifavpAny to admit basically anything, and clean up the
user-facing interface.
What do people think?
Ram
[1]: http://reviews.llvm.org/D6988