When performing call slot optimization for a non-local target, we need to check whether there may be throwing calls between the call and the copy. Otherwise, the copy may never be reached.
This was already done for call slot optimization of load/store, but not for memcpys. For the sake of clarity, I'm moving this check into the common optimization function, even if that does need an additional instruction scan for the load/store case.
clang-tidy: warning: invalid case style for parameter 'cpyLoad' [readability-identifier-naming]
not useful
clang-tidy: warning: invalid case style for parameter 'cpyStore' [readability-identifier-naming]
not useful