commit | e1ae050764fe88320e6421d2e059bc161d582e16 | [log] [tgz] |
---|---|---|
author | Johannes Doerfert <johannes@jdoerfert.de> | Thu May 18 16:46:11 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 05 17:15:31 2023 -0700 |
tree | 5cd1589662ef6d83652e1985f53d1cfc5109560e | |
parent | 806aa645a2bcfbf7442c1bc15165f95959a3b3a3 [diff] |
[Attributor] Identify and remove no-op fences The logic and implementation follows the removal of no-op barriers. If the fence is not making updates visible, either to the world or the current thread, it is not needed. Said differently, the fences we remove do not establish synchronization (happens-before) edges. This allows us to eliminate some of the regression caused by: https://reviews.llvm.org/D145290 GitOrigin-RevId: cb17c48fdd8c0f8ab6cd7ad3f197b052db20d1f6