Lines Matching full:diagnostics

6 diagnostics infrastructure.
20 The `DiagnosticEngine` acts as the main interface for diagnostics in MLIR. It
42 // that all diagnostics are consumed(i.e. a success() result).
63 diagnostics in MLIR. [`operation`](LangRef.md/#operations) provides utility
64 methods for emitting diagnostics:
107 // Diagnostics can be composed via the streaming operators.
127 To make a custom type compatible with Diagnostics, one must implement the
158 Now that [Diagnostics](#diagnostic) have been explained, we introduce the
173 diagnostics. These options can be configured via the MLIRContext, and registered
202 generated certain diagnostics. An example output is shown below:
210  #1 0x000055dd3f8ac162 emitDiag(mlir::Location, mlir::DiagnosticSeverity, llvm::Twine const&) /lib/IR/Diagnostics.cpp:292:7
211  #2 0x000055dd3f8abe8e mlir::emitError(mlir::Location, llvm::Twine const&) /lib/IR/Diagnostics.cpp:304:10
223 To interface with the diagnostics infrastructure, users will need to register a
318 certain diagnostics have been emitted to the context. To use this handler,
319 annotate your source file with expected diagnostics in the form of:
360 The handler will report an error if any unexpected diagnostics were seen, or if
361 any expected diagnostics weren't.
389 on a single thread. For diagnostics, this means that the ordering of the
390 diagnostics is the same regardless of the amount of threads being operated on.
394 each thread that will be emitting diagnostics to the handler sets a respective
395 'orderID'. The orderID corresponds to the order in which diagnostics would be
397 of operations [a, b, c] on a single-thread. Diagnostics emitted while processing
401 This provides a way for the handler to deterministically order the diagnostics
418   // Notify the handler that we are finished processing diagnostics on this