Add OR_None code to indicate that there is no overwrite. This has no any effect for current uses but will be used in one of the next patches building support for PHI translation.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Transforms/Scalar/DeadStoreElimination.cpp | ||
---|---|---|
978–979 | Adjust comment |
Looks good in general, but I couldn't find a use in the linked patches. Could you update the description with more details about the motivation, when/how this will be used.
llvm/lib/Transforms/Scalar/DeadStoreElimination.cpp | ||
---|---|---|
1378 | The comment here seems slightly inaccurate and I think it is more obvious after this change; we skip if we can't prove that there is a (partial) overwrite. Might be good to adjust the comment. | |
1389 | This seems unrelated to the patch? |
The thing is that I had to remove depending changes from the list since I didn't manage to come up with a regression test. Looks like it is not that critical and we can return to it once main functionality settles down. So let's skip this one for now as well if you don't mind :-)
Sounds good to me. Marking as changes requested so it is gone from the review queue for now.
I've encountered another case where OW_None would be helpful: D112313.
@ebrevnov I think it would be very useful to get this patch in soonish to unblock D112313 & following. I put up a variation of this patch as D112312 with a small addition: returning OW_None if both accesses do not alias. It would be good to include those here as well.
Adjust comment