JonChesterfield added a comment. There seems to be a bunch of different things in this patch.
There's some driver plumbing to compile for more than one arch (presumably by calling the target compiler N times). That's a great feature, I want to build an application bthat can run on nvptx or amdgpu. Probably need a test case showing that combination. Then there's a bunch of stuff to do with 'requirements', but it's not clear what that is. Finally there's some stuff where libomptarget dlopens itself then spawns amdgpu-arch. I can't tell why we would want to do that. My guess was that each arch would get its own section in the host executable containing a code object and each host plugin would be responsible for indicating whether it could do anything with a given code object. That should work out of the box for machines with only one offloading arch available, and need some work around device_id to handle multiple ones. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D106870/new/ https://reviews.llvm.org/D106870 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
