One option for the LIBOMPTARGET_INFO environment variable is to print the current status of the device's data mappings. These are a shared resource among threads so this needs to be protected when using multiple streams.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
openmp/libomptarget/src/private.h | ||
---|---|---|
112 | Is this stuff built with exceptions disabled? Used to seeing unlock() called from destructors. |
openmp/libomptarget/src/private.h | ||
---|---|---|
112 | This is the same thing that the Device type uses to protect the data mapping when it adds or removes something so I'm assuming it's compatible. |
openmp/libomptarget/src/private.h | ||
---|---|---|
112 | I highly doubt the runtime can recover from exceptions right now anyway. |
Is this stuff built with exceptions disabled? Used to seeing unlock() called from destructors.