saiislam added a comment. In D93525#2493752 <https://reviews.llvm.org/D93525#2493752>, @t-tye wrote:
> In D93525#2493024 <https://reviews.llvm.org/D93525#2493024>, @yaxunl wrote: > >> can you document this in ClangOffloadBundler.rst ? I think we need a clear >> description about how clang-offload-bundler knows which file in the .a file >> belongs to which target. > > How does the .a relate to bundled code objects? Does the .a have a number of > bundled code objects? If so wouldn't the identity of code objects be defined > by the existing bundled code object ABI already documented? If the .a is a > set of non-bundled code objects then defining how they are identified is not > part of the clang-offload-bundler documentation as there are no bundled code > objects involved. It would seem that the documentation belongs with the > OpenMP runtime/compiler that is choosing to use .a files in this manner. Bundles (created using clang-offload-bundler) are passed to llvm-ar to create an archive of bundled objects (*.a file). An archive can have bundles for multiple device types. So, yes, the identity of code objects is defined by the existing bundled code object ABI. This patch reads such an archive and produces a device-specific archive for each of the target devices given as input. Each device-specific archive contains all the code objects corresponding to that particular device and are written as per llvm archive format. Here is a snippet of relevant lit run lines: // RUN: %clang -O0 -target %itanium_abi_triple %s -c -o %t.o // RUN: echo 'Content of device file 1' > %t.tgt1 // RUN: clang-offload-bundler -type=o -targets=host-%itanium_abi_triple,openmp-amdgcn-amd-amdhsa-gfx900 -inputs=%t.o,%t.tgt1 -outputs=%t.abundle1.o // RUN: echo 'Content of device file 2' > %t.tgt2 // RUN: clang-offload-bundler -type=o -targets=host-%itanium_abi_triple,openmp-amdgcn-amd-amdhsa-gfx900 -inputs=%t.o,%t.tgt2 -outputs=%t.abundle2.o // RUN: llvm-ar cr %t.lib.a %t.abundle1.o %t.abundle2.o This patch ==> // RUN: clang-offload-bundler -unbundle -type=a -targets=openmp-amdgcn-amd-amdhsa-gfx900 -inputs=%t.lib.a -outputs=%t.devicelib.a %t.devicelib.a will contain all devices objects corresponding to gfx900 Though my interest originates from OpenMP side, Device-specific Archive Libraries created like this can be used by other offloading languages like HIP, CUDA, and OpenCL. Pelase refer D81109 <https://reviews.llvm.org/D81109> for the an earlier patch in the series of patches which will enable this. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D93525/new/ https://reviews.llvm.org/D93525 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
