search for: numtys

...Intrinsic::memcpy_i64), Ops, 4, "", CurBB); } The problem is that Intrinsic::getDeclaration takes four parameters but is only passed two: Function *Intrinsic::getDeclaration(Module *M, ID id, const Type **Tys, unsigned numTys) So it sees bogus data from Tys and numTys. This probably works in the official sources because the "Ops, 4" parameters to CallInst just happen to be pushed on the stack in just the right place for Intrinsic::getDeclaration. But apparently our changes to llvm here upset that delicate b...

David Greene wrote: > The problem is that Intrinsic::getDeclaration takes four > parameters but is only passed two: > > Function *Intrinsic::getDeclaration(Module *M, ID id, const Type **Tys, > unsigned numTys) It turns out that this happens all over llvm-convert.c. Tys and numTys default to zero, which is why it builds. The problem is, getDeclaration calls getType(id, Tys, numTys) where this code is executed: case Intrinsic::memcpy_i32: // llvm.memcpy.i32 case Intrinsic::memmove_i32: // llvm...

...(based on pointer to different address spaces). I am creating a new myintrinsics.td file and using the iPTRAny for the argument type. The current interface (i.e. getName() and getTyp() in Intrinsics.h) seems to require the caller to know which arguments are used for overloading, so to set Tys and numTys. This means I need to hardcode the intrinsic property in the caller, which makes the programming effort not scalable. Clang's CGBuiltin.cpp seems to do exactly that and has quite a few x86 specific knowledge baked in. I guess it is possible to provide an interface that, given an intrinsic ID,...

Julien Schmitt wrote: > I would like to use intrinsic with different address space. > I defined an intrinsic (used to represent à specific instruction of my target) with a pointer in its arguments, but when calling this intrinsic, if the pointer is not in the generic address space (ie AddrSpace 0), an error occurs ("bad signature"). > > How can I specify the address space in

I would like to use intrinsic with different address space. I defined an intrinsic (used to represent à specific instruction of my target) with a pointer in its arguments, but when calling this intrinsic, if the pointer is not in the generic address space (ie AddrSpace 0), an error occurs ("bad signature"). How can I specify the address space in the intrinsic definition ? Thank you.