Lines Matching +refs:clang +refs:format +refs:executable

33 The goal of offloading compilation is to create an executable device image that
34 can be run on the target device. OpenMP offloading creates executable images by
184 same format as the source location in the :ref:`identifier structure
225 binary format that behaves like a string map. This binary format is used to
257 create an executable device image. This is done using a Clang tool, see
268 support a relocatable object format, such as AMDGPU or SPIR-V, or if the user
277 offload code on the device. We use the :ref:`linked device executable <Device
360 describes all device images available in the executable or shared library. It
435     $ clang++ -fopenmp -fopenmp-targets=nvptx64 -O3 zaxpy.cpp -c
439 removed from the final executable or shared library by the linker.
450 Compiling this file again will invoke the ``clang-linker-wrapper`` utility to
458     $ clang++ -fopenmp -fopenmp-targets=nvptx64 zaxpy.o -o zaxpy
461 We can see the steps created by clang to generate the offloading code using the
467     $ clang++ -fopenmp -fopenmp-targets=nvptx64 -ccc-print-phases zaxpy.cpp
468     # "x86_64-unknown-linux-gnu" - "clang", inputs: ["zaxpy.cpp"], output: "/tmp/zaxpy-host.bc"
469 …# "nvptx64-nvidia-cuda" - "clang", inputs: ["zaxpy.cpp", "/tmp/zaxpy-e6a41b.bc"], output: "/tmp/za…
471 …# "x86_64-unknown-linux-gnu" - "clang", inputs: ["/tmp/zaxpy-e6a41b.bc", "/tmp/zaxpy-0af7b7.o"], o…