Revision tags: llvmorg-15.0.0-rc3 |
|
#
2f90764c |
| 24-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir:Bytecode] Add encoding support for a majority of the builtin attributes
This adds support for the non-location, non-elements, non-affine builtin attributes.
Differential Revision: https://rev
[mlir:Bytecode] Add encoding support for a majority of the builtin attributes
This adds support for the non-location, non-elements, non-affine builtin attributes.
Differential Revision: https://reviews.llvm.org/D132539
show more ...
|
#
02c2ecb9 |
| 23-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir:Bytecode] Add initial support for dialect defined attribute/type encodings
Dialects can opt-in to providing custom encodings by implementing the `BytecodeDialectInterface`. This interface prov
[mlir:Bytecode] Add initial support for dialect defined attribute/type encodings
Dialects can opt-in to providing custom encodings by implementing the `BytecodeDialectInterface`. This interface provides hooks, namely `readAttribute`/`readType` and `writeAttribute`/`writeType`, that will be used by the bytecode reader and writer. These hooks are provided a reader and writer implementation that can be used to encode various constructs in the underlying bytecode format. A unique feature of this interface is that dialects may choose to only encode a subset of their attributes and types in a custom bytecode format, which can simplify adding new or experimental components that aren't fully baked.
Differential Revision: https://reviews.llvm.org/D132498
show more ...
|
#
b3449392 |
| 23-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir:Bytecode][NFC] Cleanup Attribute/Type reading
This moves some parsing functionality from BytecodeReader to AttrTypeReader, and removes some duplication between the attribute/type code paths.
[mlir:Bytecode][NFC] Cleanup Attribute/Type reading
This moves some parsing functionality from BytecodeReader to AttrTypeReader, and removes some duplication between the attribute/type code paths.
Differential Revision: https://reviews.llvm.org/D132497
show more ...
|
#
83dc9999 |
| 23-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir:Bytecode][NFC] Refactor string section writing and reading
This extracts the string section writer and reader into dedicated classes, which better separates the logic and will also simplify fu
[mlir:Bytecode][NFC] Refactor string section writing and reading
This extracts the string section writer and reader into dedicated classes, which better separates the logic and will also simplify future patches that want to interact with the string section.
Differential Revision: https://reviews.llvm.org/D132496
show more ...
|
#
96fd3f2d |
| 22-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir:Bytecode] Fix asan failure
We were accessing the region state after it got popped from the stack.
|
#
59548fe8 |
| 22-Aug-2022 |
Goran Flegar <gflegar@google.com> |
[mlir] Fix compile errors with bytecode support
|
#
93cf0e8a |
| 22-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir] Fix bots after bytecode support was added in D131747
* Fix ambiguous Twine constructor call * Ensure shift is 64-bit (for MSVC) * Disable bytecode tests on s390x (we don't support big endian
[mlir] Fix bots after bytecode support was added in D131747
* Fix ambiguous Twine constructor call * Ensure shift is 64-bit (for MSVC) * Disable bytecode tests on s390x (we don't support big endian right now)
show more ...
|
#
f3acb54c |
| 12-Aug-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir] Add initial support for a binary serialization format
This commit adds a new bytecode serialization format for MLIR. The actual serialization of MLIR to binary is relatively straightforward,
[mlir] Add initial support for a binary serialization format
This commit adds a new bytecode serialization format for MLIR. The actual serialization of MLIR to binary is relatively straightforward, given the very very general structure of MLIR. The underlying basis for this format is a variable-length encoding for integers, which gets heavily used for nearly all aspects of the encoding (given that most of the encoding is just indexing into lists).
The format currently does not provide support for custom attribute/type serialization, and thus always uses an assembly format fallback. It also doesn't provide support for resources. These will be added in followups, the intention for this patch is to provide something that supports the basic cases, and can be built on top of.
https://discourse.llvm.org/t/rfc-a-binary-serialization-format-for-mlir/63518
Differential Revision: https://reviews.llvm.org/D131747
show more ...
|