Neil Henning 7465597060 [IRBuilder] Fixup CreateIntrinsic to allow specifying Types to Mangle. ...

The IRBuilder CreateIntrinsic method wouldn't allow you to specify the
types that you wanted the intrinsic to be mangled with. To fix this
I've:

- Added an ArrayRef<Type *> member to both CreateIntrinsic overloads.
- Used that array to pass into the Intrinsic::getDeclaration call.
- Added a CreateUnaryIntrinsic to replace the most common use of
  CreateIntrinsic where the type was auto-deduced from operand 0.
- Added a bunch more unit tests to test Create*Intrinsic calls that
  weren't being tested (including the FMF flag that wasn't checked).

This was suggested as part of the AMDGPU specific atomic optimizer
review (https://reviews.llvm.org/D51969).

Differential Revision: https://reviews.llvm.org/D52087

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@343962 91177308-0d34-0410-b5e6-96231b3b80d8

2018-10-08 10:32:33 +00:00

..

llvm

[IRBuilder] Fixup CreateIntrinsic to allow specifying Types to Mangle.

2018-10-08 10:32:33 +00:00

llvm-c

Emit template type and value parameter DIEs for template variables.

2018-10-03 18:44:53 +00:00