a9e457a82f
Summary: This was a regression from the original LLVM-gpu-loader. We used to handle `-mwavefrontsize64` correctly in the loader by over-allocating memory and just leaving the upper 32-bits masked off. In order to handle this in offload we need to scan loaded kernels to see how much memory we need to allocate. This should be safe, the protocol is designed to handle an arbitrary size and worst-case this just wastes space.
The LLVM/Offload Subproject
The Offload subproject aims at providing tooling, runtimes, and APIs that allow users to execute code on accelerators or other "co-processors" that may or may not match the architecture of their "host". In the long run, all kinds of targets are in scope of this effort, including but not limited to: CPUs, GPUs, FPGAs, AI/ML accelerators, distributed resources, etc.
For OpenMP offload users, the project is ready and fully usable. The final API design is still under development. More content will show up here and on our webpage soon. In the meantime, people are encouraged to participate in our meetings (see below) and check our development board as well as the discussions on Discourse.
Meetings
Every second Wednesday, 7:00 - 8:00am PT, starting Jan 24, 2024. Alternates with the OpenMP in LLVM meeting. invite.ics Meeting Minutes and Agenda