================ @@ -0,0 +1,27 @@ +// Verify the ELF packaging of OpenMP SPIR-V device images. +// REQUIRES: system-linux +// REQUIRES: spirv-tools +// REQUIRES: spirv-registered-target +// REQUIRES: x86-registered-target + +// RUN: %clang -cc1 %s -triple x86_64-unknown-linux-gnu -emit-llvm-bc -o %t.bc +// RUN: %clang -cc1 %s -triple spirv64-intel -fopenmp-is-target-device -o %t.device.o +// RUN: llvm-offload-binary -o %t.bundle --image=file=%t.device.o,triple=spirv64-intel,arch=generic,kind=openmp +// RUN: %clang -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -fembed-offload-object=%t.bundle -x ir %t.bc -o %t.host.o ---------------- YuriPlyakhin wrote:
I don't think this test is testing llvm-objdump functionality introduced in #185425 . And yes, I agree that `clang-linker-wrapper-spirv.cpp` test should not belong to #185425 . The test is rather testing this pr: https://github.com/llvm/llvm-project/pull/125737 . #185425 just extended llvm-objdump, so the `clang-linker-wrapper` functionality introduced in #125737 can be tested. full history: https://github.com/llvm/llvm-project/pull/125737 - adds new clang-linker-wrapper functionality, adds new test: `clang/test/Tooling/clang-linker-wrapper-spirv-elf.cpp` https://github.com/llvm/llvm-project/pull/185413 - changes clang-linker-wrapper functionality, removes `clang/test/Tooling/clang-linker-wrapper-spirv-elf.cpp`, merged without any test. https://github.com/llvm/llvm-project/pull/185425 - adds llvm-objdump functionality and tests for it, but also returns back clang-linker-wrapper test with this name: `clang/test/Tooling/clang-linker-wrapper-spirv.cpp` So I still think this is a clang-linker-wrapper test. https://github.com/llvm/llvm-project/pull/198434 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
