Closed jckarter closed 11 years ago
LLVM 3.2 changed how LLVM intrinsics are registered. Per @crabtw:
You can use getIntrinsicInfoTableEntries to get the information (https://gist.github.com/4432544#file-intrinsics-diff-L121) and the first entry of table is for output type. It uses Verifier::VerifyIntrinsicType to verify intrinsic types (https://gist.github.com/4432544#file-intrinsics-diff-L30).
You can use getIntrinsicInfoTableEntries to get the information (https://gist.github.com/4432544#file-intrinsics-diff-L121) and the first entry of table is for output type.
It uses Verifier::VerifyIntrinsicType to verify intrinsic types (https://gist.github.com/4432544#file-intrinsics-diff-L30).
Clay's loadIntrinsicsModule implementation needs to be updated to correctly populate __intrinsics__ under LLVM 3.2.
loadIntrinsicsModule
__intrinsics__
Done by @crabtw in #479.
LLVM 3.2 changed how LLVM intrinsics are registered. Per @crabtw:
Clay's
loadIntrinsicsModule
implementation needs to be updated to correctly populate__intrinsics__
under LLVM 3.2.