llvm-project.git/mlir/lib/CAPI/IR/Diagnostics.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [mlir] Move diagnostic handlers instead of copying 2022-05-21T11:25:24+00:00 Benjamin Kramer benny.kra@googlemail.com 2022-05-21T11:25:24+00:00 295d032762ad284068c72cc1904680a4db5e80d3 This also allows using unique_ptr instead of shared_ptr for the CAPI user data. NFCI. 
This also allows using unique_ptr instead of shared_ptr for the CAPI
user data. NFCI.
Fix more clang-tidy cleanups in mlir/ (NFC) 2021-12-22T20:53:11+00:00 Mehdi Amini joker.eph@gmail.com 2021-12-22T00:19:53+00:00 e5639b3fa45f68c53e8e676749b0f1aacd16b41d 






Add userData to the diagnostic handler C API
2020-11-23T17:52:45+00:00

George


2020-11-23T17:52:17+00:00

0c5cff300ffa1d5cc55f2b11e4546f18b3389aa6

Previously, there was no way to add context to the diagnostic engine via the C API. Adding this ability makes it much easier to reason about memory ownership, particularly in reference-counted languages such as Swift. There are more details in the review comments.

Reviewed By: ftynse, mehdi_amini

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





Previously, there was no way to add context to the diagnostic engine via the C API. Adding this ability makes it much easier to reason about memory ownership, particularly in reference-counted languages such as Swift. There are more details in the review comments.

Reviewed By: ftynse, mehdi_amini

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







Switch the CallbackOstream wrapper in the MLIR C API to an Unbuffered stream
2020-11-04T06:36:32+00:00

Mehdi Amini
joker.eph@gmail.com

2020-11-03T23:46:42+00:00

b4fa6d3e13ef66baec8c2610c5ce39f3e470da12

This delegate the control of the buffering to the user of the API. This
seems like a safer option as messages are immediately propagated to the
user, which may lead to less surprising behavior during debugging for
instance.
In terms of performance, a user can add a buffered stream on the other
side of the callback.

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





This delegate the control of the buffering to the user of the API. This
seems like a safer option as messages are immediately propagated to the
user, which may lead to less surprising behavior during debugging for
instance.
In terms of performance, a user can add a buffered stream on the other
side of the callback.

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







[mlir] Add support for diagnostics in C API.
2020-10-07T12:42:02+00:00

Alex Zinenko
zinenko@google.com

2020-10-07T12:38:10+00:00

7b5dfb400a67f03122b43cd5d59b8b1ef6d00147

Add basic support for registering diagnostic handlers with the context
(actually, the diagnostic engine contained in the context) and processing
diagnostic messages from the C API.

Reviewed By: stellaraccident

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





Add basic support for registering diagnostic handlers with the context
(actually, the diagnostic engine contained in the context) and processing
diagnostic messages from the C API.

Reviewed By: stellaraccident

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