summaryrefslogtreecommitdiffstats
path: root/mlir/lib/Dialect/SPIRV/Serialization/Serializer.cpp
diff options
context:
space:
mode:
authorRiver Riddle <riverriddle@google.com>2019-11-12 11:57:47 -0800
committerA. Unique TensorFlower <gardener@tensorflow.org>2019-11-12 11:59:19 -0800
commit626e1fd95e626c47154c5fe5d546f3d36b39e319 (patch)
tree5b2172eb1f88ed79c97bae056456b95b45332eca /mlir/lib/Dialect/SPIRV/Serialization/Serializer.cpp
parentaa9dc9446e21b0de1389d460a41867ade7bc4683 (diff)
downloadbcm5719-llvm-626e1fd95e626c47154c5fe5d546f3d36b39e319.tar.gz
bcm5719-llvm-626e1fd95e626c47154c5fe5d546f3d36b39e319.zip
Add an option to print an operation if a diagnostic is emitted on it
It is often helpful to inspect the operation that the error/warning/remark/etc. originated from, especially in the context of debugging or in the case of a verifier failure. This change adds an option 'mlir-print-op-on-diagnostic' that attaches the operation as a note to any diagnostic that is emitted on it via Operation::emit(Error|Warning|Remark). In the case of an error, the operation is printed in the generic form. PiperOrigin-RevId: 280021438
Diffstat (limited to 'mlir/lib/Dialect/SPIRV/Serialization/Serializer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud