search for: anymemsetinst

...f we go the multiple inheritance route, then what about something like: MemIntrinsic * MemSetInst * MemTransferInst ** MemCpyInst ** MemMoveInst AtomicMemIntrinsic * AtomicMemSetInst * AtomicMemTransferInst ** AtomicMemCpyInst ** AtomicMemMoveInst AnyMemIntrinsic : MemIntrinsic, AtomicMemIntrinsic AnyMemSetInst : MemSetInst, AtomicMemSetInst AnyMemTransferInst : MemTranferInst, AtomicMemTransferInst … etc. That would leave the meanings of the current MemIntrinsic classes completely unchanged; which should be good for 3rd parties. Updating a pass to work with unordered-atomic memory intrinsics would just...

Hi all, We somewhat recently created/updated element-wise unordered-atomic versions of the memcpy, memmove, and memset memory intrinsics: Memcpy: https://reviews.llvm.org/rL305558 Memmove: https://reviews.llvm.org/rL307796 Memset: https://reviews.llvm.org/rL307854 These intrinsics are semantically similar to the regular versions. The main difference is that the underlying operation is performed