Vectorization of library calls was unnecessarily fragile as
LoopAccessAnalysis would only consult the hardcoded list of
vectorizable functions for (call) instructions marked as potentially
reading from memory. However, few of the library functions in
llvm/include/llvm/Analysis/VecFuncs.def actually do that.
Thus commit ea75be3d9df448b6abafaf752a8141764d93ca33 and its
recommit 5f0a349738304caf5f8083166f785a91048f574d broke library
call vectorization by correctly declaring many library functions
as write only.
Apply the obvious fix of considering any call for vectorization,
not just those to functions that may read from memory.
Also change the libm-vector-calls tests so they would have
caught the issue.
clang-format not found in user’s local PATH; not linting file.