Displaying 2 results from an estimated 2 matches for "modifyingaccess".
2016 Jun 27
0
[MemorySSA] Potential bug in MemoryUse defining access calculation
This is definitely a caching bug related to this code:
1038 // Don't try to optimize this phi again if we've already tried
to do so.
1039 if (!Q.Visited.insert(PHIPair).second) {
1040 ModifyingAccess = CurrAccess;
1041 break;
1042 }
We don't differentiate elsewhere between having stopped at a phi because we
were path walking and discovered that path has no conflicts, and having
stopped at a phi because that was the clobbering access.
Because of this, we cache the result as...
2016 Jun 27
2
[MemorySSA] Potential bug in MemoryUse defining access calculation
Hey All,
I've come across what I believe to be a bug in MemorySSA. George, I
wasn't sure if this was a known issue that you'll be addressing in your
upcoming walker caching changes or not, so I haven't investigated it
very much. The test case is attached. The bug is that the defining
access for the second load is set to the loop MemoryPhi node instead of
being liveOnEntry as