[PATCH] [LoopAccesses] Cache the result of canVectorizeMemory
anemet at apple.com
Mon Feb 16 17:05:37 PST 2015
In http://reviews.llvm.org/D7682#124581, @hfinkel wrote:
> Why not do the analysis in the constructor, and remove the implicit ordering dependency between calling analyzeLoop and calling the other accessor functions?
I think that should work, let me give it a try.
More information about the llvm-commits