Displaying 2 results from an estimated 2 matches for "c053964f".
Did you mean:
c043464f
2016 Jun 27
0
[MemorySSA] Potential bug in MemoryUse defining access calculation
...Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160627/c053964f/attachment.html>
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