You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LLVM target triples can be with or without the optional environment field:
269
+
The bundler accepts target triples with or without the optional environment
270
+
field:
270
271
271
272
``<arch><sub>-<vendor>-<sys>``, or
272
273
``<arch><sub>-<vendor>-<sys>-<env>``
273
274
274
-
However, in order to standardize outputs for tools that consume bitcode bundles
275
-
and to parse target ID containing dashes, the bundler only accepts target
276
-
triples in the 4-field format:
275
+
However, in order to standardize outputs for tools that consume bitcode
276
+
bundles, bundles written by the bundler internally use only the 4-field
277
+
target triple:
277
278
278
279
``<arch><sub>-<vendor>-<sys>-<env>``
279
280
@@ -542,4 +543,4 @@ The compressed offload bundle begins with a header followed by the compressed bi
542
543
- **Compressed Data**:
543
544
The actual compressed binary data follows the header. Its size can be inferred from the total size of the file minus the header size.
544
545
545
-
> **Note**: Version 3 of the format is under development. It uses 64-bit fields for Total File Size and Uncompressed Binary Size to support files larger than 4GB. To experiment with version 3, set the environment variable `COMPRESSED_BUNDLE_FORMAT_VERSION=3`. This support is experimental and not recommended for production use.
546
+
> **Note**: Version 3 of the format is under development. It uses 64-bit fields for Total File Size and Uncompressed Binary Size to support files larger than 4GB. To experiment with version 3, set the environment variable `COMPRESSED_BUNDLE_FORMAT_VERSION=3`. This support is experimental and not recommended for production use.
0 commit comments