Lines Matching refs:bytecode

3 This document describes the MLIR bytecode format and its encoding.
6 older bytecode. Similarly, we support back-deployment so that an
10 bytecode format are made assuming immutable dialects: the format
16 to allow managing a version encoded into the bytecode file. The
29 indicate bytecode files:
59 represent a single 64-bit value. The MLIR bytecode utilizes the "PrefixVarInt"
122 Sections are a mechanism for grouping data within the bytecode. They enable
132 Given the generic structure of MLIR, the bytecode encoding is actually fairly
137 The top-level structure of the bytecode contains the 4-byte "magic number", a
139 section is currently only expected to appear once within a bytecode file.
142 bytecode {
160 The string section contains a table of strings referenced within the bytecode,
168 The dialect section of the bytecode contains all of the dialects referenced
242 the textual assembly format, or a custom bytecode encoding. We avoid using the
258 fallback. For example, a type `!bytecode.type<42>` would be encoded as the null
259 terminated string "!bytecode.type<42>". This ensures that every attribute and
275 by the bytecode reader and writer. These hooks are provided a reader and writer
277 bytecode format. A unique feature of this interface is that dialects may choose
278 to only encode a subset of their attributes and types in a custom bytecode
282 When implementing the bytecode interface, dialects are responsible for all
284 or type is being encoded; the bytecode reader will only know that it has
341 The IR section contains the encoded form of operations within the bytecode.
385 commonly appearing structure in the bytecode. A single encoding is used for
424 parsing the bytecode. The encoding represents an index map from the reference
433 bytecode memory requirements.