[LV] Fix analyzeInterleaving when -pass-remarks enabled

[mtrofin]

Summary

If -pass-remarks=loop-vectorize, atomic ops will be seen by
analyzeInterleaving(), even though canVectorizeMemory() == false. This
is because we are requesting extra analysis instead of bailing out.

In such a case, we end up with a Group in both Load- and StoreGroups,
and then we'll try to access freed memory when traversing LoadGroups after having had released the Group when iterating over StoreGroups.

The fix is to include mayWriteToMemory() when validating that two
instructions are the same kind of memory operation.

[davidxl]

lib/Transforms/Vectorize/LoopVectorize.cpp

5929

s/exclussive/exclusive/

5933

Add a test case?

[hsaito]

lib/Transforms/Vectorize/LoopVectorize.cpp

5931–5932

The root-cause of this problem is the fact that Interleaved Access Analysis is invoked as part of legality check ---- most likely because the original developer did not want to pass one extra arg to CostModel, etc., decided to keep InterleaveInfo in Legality class, and reviewers did not object to it. I'm currently working on a change set to address this architectural problem (i.e., optimization/cost model related work done in legal) by moving interleave access analysis outside of Legality.

Having said that, tightening "same kind of memory operation" check is a good thing to have even after the above mentioned refactoring is done.

[mtrofin]

Added test.

[mtrofin]

Removed blank line.

[mtrofin]

lib/Transforms/Vectorize/LoopVectorize.cpp

5931–5932

Thank you for the insight!

[mtrofin]

Ping - Thanks!

[davidxl]

lgtm

lib/Transforms/Vectorize/LoopVectorize.cpp

for (auto AI = std::next(BI); AI != E; ++AI) {
 
       // At this point, we've checked for illegal code motion. If either A or B
       // isn't strided, there's nothing left to do.
       if (!isStrided(DesA.Stride) || !isStrided(DesB.Stride))
         continue;
 
       // Ignore A if it's already in a group or isn't the same kind of memory
       // operation as B.
-      if (isInterleaved(A) || A->mayReadFromMemory() != B->mayReadFromMemory())
+      // Note that mayReadFromMemory() isn't mutually exclussive to mayWriteToMemory
+      // in the case of atomic loads. We shouldn't see those here, canVectorizeMemory()
+      // should have returned false - except for the case we asked for optimization
+      // remarks.
+      if (isInterleaved(A) || (A->mayReadFromMemory() != B->mayReadFromMemory())
+          || (A->mayWriteToMemory() != B->mayWriteToMemory()))
         continue;
 
       // Check rules 1 and 2. Ignore A if its stride or size is different from
       // that of B.
       if (DesA.Stride != DesB.Stride || DesA.Size != DesB.Size)
         continue;
 
       // Ignore A if the memory object of A and B don't belong to the same