Lines Matching +refs:clang +refs:format +refs:extract

37 object. A special tool then needs to extract the device code from the fat
59   and extract the device objects. Run the device linking action on the extracted
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
268 support a relocatable object format, such as AMDGPU or SPIR-V, or if the user
435     $ clang++ -fopenmp -fopenmp-targets=nvptx64 -O3 zaxpy.cpp -c
450 Compiling this file again will invoke the ``clang-linker-wrapper`` utility to
451 extract and link the device code stored at the section named
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…