llvm-project
bdf5b9c5 - [offload][omp] Manage memory allocation through liboffload

Commit
7 days ago
[offload][omp] Manage memory allocation through liboffload Migrate DeviceTy::allocData/deleteData off GenericPluginTy::data_alloc/ data_delete onto liboffload's olMemAlloc*/olMemFree, migrate targetLockExplicit/targetUnlockExplicit off data_lock/data_unlock onto olMemRegister/olMemUnregister (fixing a latent bug where these passed the OpenMP-visible device number instead of the plugin device id), and migrate DeviceTy::isAccessiblePtr onto a new olMemIsAccessible API (added with a unit test) since liboffload had no equivalent for querying accessibility of arbitrary, not-necessarily-liboffload- allocated pointers. Removes the now-dead GenericPluginTy::data_alloc/ data_delete/data_lock/data_unlock/is_accessible_ptr wrappers and their exports entries.
Author
Committer
Parents
Loading