Lines Matching refs:host

35 compiling the input file for both the host and the target device. The output
36 from the device phase then needs to be embedded into the host to create a fat
39 host runtime library can use to register the library and access the symbols on
48 * Compile the input file for the host to produce a bitcode file. Lower ``#pragma
53   by the host.
56 * Run the backend on the host bitcode file and create a :ref:`fat object file
63   can be accessed by the host.
65   run the host linking action. Link with ``libomptarget`` to register and
73 The first step in compilation is to generate offloading entries for the host.
150 table mapping host pointers to device pointers. Global variables inside a
151 ``#pragma omp target declare`` directive are first initialized to the host's
153 map the host address to the device address.
194 compilation stage is performed differently from the host stage. Namely, we do
196 ``-fopenmp-is-device`` flag to the front-end. We use the host bitcode to
198 from the previous stage using the ``-fopenmp-host-ir-file-path`` flag.
203 class of errors where a symbol in the target device could preempt a host
213 create a relocatable device object file that can be embedded in the host.
222 stage into the host as a named section. The output from the device compilation
223 is passed to the host backend using the ``-fembed-offload-object`` flag. This
235 is run on the host, creating a fat object. Using fat objects allows us to treat
236 offloading objects as standard host objects. The final object file should
259 over the host linking job. It scans the input object files for the offloading
263 the device image and link it with the host.
266 optimization (LTO). This is used whenever the object files embedded in the host
319     | __tgt_offload_entry* | HostEntriesBegin | Begin of table with all host entries     |
468     # "x86_64-unknown-linux-gnu" - "clang", inputs: ["zaxpy.cpp"], output: "/tmp/zaxpy-host.bc"