[PATCH] D25276: [LoopVectorizer] Interleaved-mem-accesses analysis and getPtrStride

Matthew Simpson via llvm-commits llvm-commits at lists.llvm.org
Wed Oct 19 07:50:58 PDT 2016

mssimpso added a comment.

Hi Dorit/Silviu,

Intuitively it seems like we would want to use getPtrStride in the interleaved access analysis the same way we do in isConsecutivePtr. Is the issue here that we might add additional run-time checks that we aren't currently? We already call isConsecutivePtr for the pointer operand of every load/store in the loop. Would the additional checks then be duplicates?


More information about the llvm-commits mailing list