Lines Matching full:image

13 This tool bundles device files into a single image containing necessary
15 together. The image format is a small header wrapping around a string map. This
26 format is a serialization of a string map and an image buffer. The binary header
47 of the binary blob containing the information for a single offloading image. We
49 the image and metadata. The offload entry contains information about the device
50 image. It contains the fields shown in the following
59     | uint16_t |  image kind   | The kind of the device image (e.g. bc, cubin)      |
61     | uint16_t | offload kind  | The producer of the image (e.g. openmp, cuda)      |
63     | uint32_t |     flags     | Generic flags for the image                        |
69     | uint64_t |  image offset | Absolute offset of the device image in bytes       |
71     | uint64_t |   image size  | Size of the device image in bytes                  |
74 This table contains the offsets of the string table and the device image itself
75 along with some other integer information. The image kind lets us easily
76 identify the type of image stored here without needing to inspect the binary.
78 semantics are necessary for this image. These are stored as enumerations with
80 :ref:`image kind<table-image_kind>`.
82 .. table:: Image Kind
88     | IMG_None      | 0x00  | No image information provided         |
90     | IMG_Object    | 0x01  | The image is a generic object file    |
92     | IMG_Bitcode   | 0x02  | The image is an LLVM-IR bitcode file  |
94     | IMG_Cubin     | 0x03  | The image is a CUDA object file       |
96     | IMG_Fatbinary | 0x04  | The image is a CUDA fatbinary file    |
98     | IMG_PTX       | 0x05  | The image is a CUDA PTX file          |
134 terminated strings with defined offsets in the image. The string entry allows us
136 arbitrary arguments to the image, such as the triple and architecture.
142 the magic bytes and size of each image, we can extract them as-needed.
148 passed as a key-value pair to the ``image=`` argument. The ``file`` and
149 ``triple``, arguments are considered mandatory to make a valid image.
170     --image=<<key>=<value>,...> - List of key and value arguments. Required
177 This tool simply takes many input files from the ``image`` option and creates a
182   clang-offload-packager -o out.bin --image=file=input.o,triple=nvptx64,arch=sm_70
187 will be generated for each matching image.
191   clang-offload-packager in.bin --image=file=output.o,triple=nvptx64,arch=sm_70