search for: creatememmoveloop

...lso now invoked with different source & dest alignments by LowerMemIntrinsics, rather than the same alignment for both, so these helpers will now be invoked with more information than they have in the past; I’m guessing that it’s possible they could do better with this information. For example, createMemMoveLoop() doesn’t even use the alignments it’s given at all right now, and the neither of the createMemCpyLoop*() functions try to set the alignments on the loads & stores it creates. Passes that have conservative alignments after updating: - SelectionDAG - AArch64FastISel - ARMFastISel - MemorySaniti...

...different source & dest > alignments by LowerMemIntrinsics, rather than the same alignment for both, so > these helpers will now be invoked with more information than they have in the > past; I’m guessing that it’s possible they could do better with this > information. For example, createMemMoveLoop() doesn’t even use the alignments > it’s given at all right now, and the neither of the createMemCpyLoop*() > functions try to set the alignments on the loads & stores it creates. > > Passes that have conservative alignments after updating: > - SelectionDAG > - AArch64FastISe...

Good day all, I’ve spent a few days resurrecting the circa-2015 work on removing the explicit alignment argument (4th arg) from the @llvm.memcpy/memmove/memset intrinsics in favour of using the alignment attribute on the pointer args of calls to the intrinsic. This work was first proposed back in August 2015 by Lang Hames: http://lists.llvm.org/pipermail/llvm-dev/2015-August/089384.html (item

...ildCall 2 llvm::fuzzerop::sizedPtrType 2 llvm::MemCpyOptPass::processByValArgument 2 createMemMoveLoop 2 cloneConstantExprWithNewAddressSpace 2 llvm::FastISel::lowerCallTo 2 llvm::RISCV...