Displaying 3 results from an estimated 3 matches for "llvm_any_typ".
Did you mean:
llvm_any_ty
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
Hi,
So, we currently have gc.result.int, gc.result.float. gc.result.ptr,
gc.relocate, and gc.statepoint. gc.statepoint's signature is fine with
a iPTRAny as the first argument. gc.result is in trouble, because none
of the signatures admit even a simple array of integers, and there's
no aAny. And certainly no vectors. So we can get a gc.result.vector to
add to this mess, and admit [1] to
2018 Dec 31
1
Issue with "t -> signature is meaningless, use custom typechecking"
Hello,
I was implementing the llvm_any_type in my intrinsic
def int_csa_xxx : Intrinsic<[llvm_any_ty], [llvm_i32_ty]>;
as the following in its corresponding builtins in Builtins.def:
BUILTIN(__builtin_xxx, "v.", "nt")
the "t" was sufficient here to not perform any type checking.
The type checking was...