Hi all,
Some of my colleagues and I are currently developing the infrastructure for adding a new device, the cloud, to the list of available targets. Considering the cloud as a device requires few changes to the API of the offloading library (libomptarget). Indeed, our cloud device handles offloading data thanks to files instead of values within an address space. To do so, we had to associate each offloaded variables with a unique identifier. Those identifiers are assigned by Clang to each variable, then transmitted to libomptarget as an additional argument of the offloading function “__tgt_target”. In case of pointer addresses that are not generated by Clang, the special identifier “-1” is attributed. This allows us to easily skip the offloading of these addresses that our device doesn’t use.
You can find attached the patches including the needed modifications both for Clang and libomptarget (based on the repositories of https://github.com/clang-omp/). If needed, I can make a push request directly in github.
Let’s us precise that we plan to open source all this work and to submit patches to the upstream Clang/OpenMP repositories when it will be mature enough. Additionally to simplify future integrations, those API changes can be helpful for any exotic offloading target. That’s why we propose to integrate them directly.
Regards,
libomptarget-identifiers.patch (20.2 KB)
clang-identifiers.patch (11.9 KB)
