search for: iswriteptr

Hi Ashutosh, Have you been following the recent Loop Access Analysis work? LAA was split out from the Loop Vectorizer that have been performing the kind of loop versioning that you describe. The main reason was to be able to share this functionality with other passes. Loop Access Analysis is an analysis pass that computes basic memory dependence and the runtime checks. The versioning decision

...gt; > 2) > In "RuntimeCheckEmitter::addRuntimeCheck" following 3 condition needs to > controlled by above conditional variables. > > a> > Change Following Check: > // No need to check if two readonly pointers intersect. > if (!PtrRtCheck->IsWritePtr[i] && !PtrRtCheck->IsWritePtr[j]) > continue; > To: > // No need to check if two readonly pointers intersect. > if (!CheckReadOnlyPointersIntersection && !PtrRtCheck->IsWritePtr[i] && > !PtrRtCheck->IsWr...

I like to propose a new loop multi versioning optimization for LICM. For now I kept this for LICM only, but it can be used in multiple places. The main motivation is to allow optimizations stuck because of memory alias dependencies. Most of the time when alias analysis is unsure about memory access and it says may-alias. This un surety from alias analysis restrict some of the memory based