[PATCH] D30225: [LIR] re-enable generation of memmove with runtime checks

[Eli Friedman via Phabricator via llvm-commits]

efriedma added a comment.

Why are we generating a runtime check for memmove, as opposed to memcpy?  I mean, they're the same function on many platforms, but we inline calls to memcpy much more aggressively for small sizes, so there could be a performance benefit to generating llvm.memcpy instead of llvm.memmove.

Does it make sense to perform this transform as part of the loop-idiom pass?  loop-idiom runs interleaved with inlining; inserting runtime checks before we inline a function seems like a bad idea.


Repository:
  rL LLVM

https://reviews.llvm.org/D30225