llvm-project.git/mlir/test/Bytecode/bytecode_callback_with_custom_attribute.mlir, branch main Unnamed repository; edit this file 'description' to name the repository. [mlir][bytecode] Implements back deployment capability for MLIR dialects (#70724) 2023-10-31T22:41:29+00:00 Matteo Franciolini m_franciolini@apple.com 2023-10-31T22:41:29+00:00 7ad9e9dcf518431a8ecedcc06b09df6c799658ef When emitting bytecode, clients can specify a target dialect version to emit in `BytecodeWriterConfig`. This exposes a target dialect version to the DialectBytecodeWriter, which can be queried by name and used to back-deploy attributes, types, and properties. 
When emitting bytecode, clients can specify a target dialect version to
emit in `BytecodeWriterConfig`. This exposes a target dialect version to
the DialectBytecodeWriter, which can be queried by name and used to
back-deploy attributes, types, and properties.
 Expose callbacks for encoding of types/attributes 2023-07-28T23:45:42+00:00 Matteo Franciolini m_franciolini@apple.com 2023-07-28T17:43:51+00:00 bff6a4292f80d058c9eaf17c2b0532a780757cec [mlir] Expose a mechanism to provide a callback for encoding types and attributes in MLIR bytecode. Two callbacks are exposed, respectively, to the BytecodeWriterConfig and to the ParserConfig. At bytecode parsing/printing, clients have the ability to specify a callback to be used to optionally read/write the encoding. On failure, fallback path will execute the default parsers and printers for the dialect. Testing shows how to leverage this functionality to support back-deployment and backward-compatibility usecases when roundtripping to bytecode a client dialect with type/attributes dependencies on upstream. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D153383 
[mlir] Expose a mechanism to provide a callback for encoding types and attributes in MLIR bytecode.

Two callbacks are exposed, respectively, to the BytecodeWriterConfig and to the ParserConfig. At bytecode parsing/printing, clients have the ability to specify a callback to be used to optionally read/write the encoding. On failure, fallback path will execute the default parsers and printers for the dialect.

Testing shows how to leverage this functionality to support back-deployment and backward-compatibility usecases when roundtripping to bytecode a client dialect with type/attributes dependencies on upstream.

Reviewed By: rriddle

Differential Revision: https://reviews.llvm.org/D153383
Revert "Expose callbacks for encoding of types/attributes" 2023-07-28T23:45:42+00:00 Mehdi Amini joker.eph@gmail.com 2023-07-28T23:44:25+00:00 b86a13211fcd84bfae39066b51f9f079f970cea8 This reverts commit b299ec16661f653df66cdaf161cdc5441bc9803c. The authorship informations were incorrect. 
This reverts commit b299ec16661f653df66cdaf161cdc5441bc9803c.

The authorship informations were incorrect.
Expose callbacks for encoding of types/attributes 2023-07-28T17:44:02+00:00 Mehdi Amini joker.eph@gmail.com 2023-07-28T17:43:51+00:00 b299ec16661f653df66cdaf161cdc5441bc9803c [mlir] Expose a mechanism to provide a callback for encoding types and attributes in MLIR bytecode. Two callbacks are exposed, respectively, to the BytecodeWriterConfig and to the ParserConfig. At bytecode parsing/printing, clients have the ability to specify a callback to be used to optionally read/write the encoding. On failure, fallback path will execute the default parsers and printers for the dialect. Testing shows how to leverage this functionality to support back-deployment and backward-compatibility usecases when roundtripping to bytecode a client dialect with type/attributes dependencies on upstream. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D153383 
[mlir] Expose a mechanism to provide a callback for encoding types and attributes in MLIR bytecode.

Two callbacks are exposed, respectively, to the BytecodeWriterConfig and to the ParserConfig. At bytecode parsing/printing, clients have the ability to specify a callback to be used to optionally read/write the encoding. On failure, fallback path will execute the default parsers and printers for the dialect.

Testing shows how to leverage this functionality to support back-deployment and backward-compatibility usecases when roundtripping to bytecode a client dialect with type/attributes dependencies on upstream.

Reviewed By: rriddle

Differential Revision: https://reviews.llvm.org/D153383