maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/mlir/test/IR/print-op-on-diagnostic.mlir

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

8 lines
284 B
MLIR
Raw Normal View History

[mlir][IR] Manually register command line options for MLIRContext and AsmPrinter Summary: This revision makes the registration of command line options for these two files manual with `registerMLIRContextCLOptions` and `registerAsmPrinterCLOptions` methods. This removes the last remaining static constructors within lib/. Differential Revision: https://reviews.llvm.org/D77960
2020-04-12 14:11:51 +08:00
// RUN: not mlir-opt %s -mlir-print-op-on-diagnostic 2>&1 | FileCheck %s
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
2019-11-13 03:57:47 +08:00
// This file tests the functionality of 'mlir-print-op-on-diagnostic'.
[mlir][IR] Manually register command line options for MLIRContext and AsmPrinter Summary: This revision makes the registration of command line options for these two files manual with `registerMLIRContextCLOptions` and `registerAsmPrinterCLOptions` methods. This removes the last remaining static constructors within lib/. Differential Revision: https://reviews.llvm.org/D77960
2020-04-12 14:11:51 +08:00
// CHECK: {{invalid to use 'test.invalid_attr'}}
// CHECK: {{see current operation: "module"()}}
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
2019-11-13 03:57:47 +08:00
module attributes {test.invalid_attr} {}