forked from OSchip/llvm-project
b316126887
If we decided to delete a mapping entry we did not act on it right away but first issued and waited for memory copies. In the meantime some other thread might reuse the entry. While there was some logic to avoid colliding on the actual "deletion" part, there were two races happening: 1) The data transfer back of the thread deleting the entry and the data transfer back of the thread taking over the entry raced. 2) The update to the shadow map happened regardless if the entry was actually reused by another thread which left the shadow map in a inconsistent state. To fix both issues we will now update the shadow map and delete the entry only if we are sure the thread is responsible for deletion, hence no other thread took over the entry and reused it. We also wait for a potential former data transfer from the device to finish before we issue another one that would race with it. Fixes https://github.com/llvm/llvm-project/issues/54216 Differential Revision: https://reviews.llvm.org/D121058 |
||
|---|---|---|
| .. | ||
| Debug.h | ||
| DeviceEnvironment.h | ||
| ExclusiveAccess.h | ||
| SourceInfo.h | ||
| device.h | ||
| dlwrap.h | ||
| interop.h | ||
| omptarget.h | ||
| omptargetplugin.h | ||
| rtl.h | ||