[PATCH] D20789: Consecutive memory access in Loop Vectorizer - fixed and simplified
email@example.com via llvm-commits
llvm-commits at lists.llvm.org
Mon Jun 13 07:35:56 PDT 2016
sbaranga added a comment.
It looks like we don't care if the pointer is wrapping in isConsecutivePtr, but getPtrStride is testing it since this is required for LAA?
In that case it might be better to either factor out the wrapping checks from getPtrStride or change the interface so that getPtrStride takes an Assume parameter and a ShouldCheckWrap parameter?
More information about the llvm-commits