-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix visitPHINode for PatchPeepholeOpt #1108
Fix visitPHINode for PatchPeepholeOpt #1108
Conversation
Test summary for commit b083d4fDriver commits used in build
CTS tests (Failed: 0/192520)
Rhel 8.2, Gfx10Ubuntu 18.04, Gfx9Ubuntu 20.04, Gfx8Ubuntu 20.04, Gfx103 |
a6225e2
to
7e70df6
Compare
Thanks for adding the test, that's really helpful to know the breaking case. The patch itself looks good. But I think it would be better to further investigate why this optimization was there. Currently we check against most known |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change a comment : // Do not clone allocas, atomics and instructions with side effects and memory reading
add // TODO PeepholeOpt. of ruiling comment
7e70df6
to
4e893ba
Compare
retest this please |
PHI with incoming value that may read from memory should not be optimized, because whether the memory content is changed is unknown, the same load may produce different values in each incoming block. Also add a lgc test for it.
retest this please |
4e893ba
to
d69b9e1
Compare
retest this please |
Test summary for commit d69b9e1Driver commits used in build
CTS tests (Failed: 0/222489)
Rhel 8.2, Gfx10Ubuntu 18.04, Gfx9Ubuntu 20.04, Gfx8Ubuntu 20.04, Gfx103 |
PHI with incoming value that may read from memory should not be optimized, because whether the memory content is changed is unknown, the same load may produce different values in each incoming block.