Searched refs:DiagnosticEngine (Results 1 – 6 of 6) sorted by relevance
207 llvm::SmallMapVector<DiagnosticEngine::HandlerID, DiagnosticEngine::HandlerTy,213 DiagnosticEngine::HandlerID uniqueHandlerId = 1;248 DiagnosticEngine::DiagnosticEngine() : impl(new DiagnosticEngineImpl()) {} in DiagnosticEngine() function in DiagnosticEngine249 DiagnosticEngine::~DiagnosticEngine() {} in ~DiagnosticEngine()254 auto DiagnosticEngine::registerHandler(const HandlerTy &handler) -> HandlerID { in registerHandler()262 void DiagnosticEngine::eraseHandler(HandlerID handlerID) { in eraseHandler()269 void DiagnosticEngine::emit(Diagnostic diag) { in emit()886 DiagnosticEngine::HandlerID handlerID;
224 DiagnosticEngine diagEngine;413 DiagnosticEngine &MLIRContext::getDiagEngine() { return getImpl().diagEngine; } in getDiagEngine()
26 class DiagnosticEngine; variable361 InFlightDiagnostic(DiagnosticEngine *owner, Diagnostic &&rhs) in InFlightDiagnostic()372 friend DiagnosticEngine; variable375 DiagnosticEngine *owner = nullptr;389 class DiagnosticEngine {391 ~DiagnosticEngine();447 DiagnosticEngine();517 DiagnosticEngine::HandlerID handlerID;
20 class DiagnosticEngine; variable140 DiagnosticEngine &getDiagEngine();
63 DiagnosticEngine::HandlerID id = in mlirContextAttachDiagnosticHandler()74 static_cast<DiagnosticEngine::HandlerID>(id)); in mlirContextDetachDiagnosticHandler()
80 The `DiagnosticEngine` acts as the main interface for diagnostics in MLIR. It89 DiagnosticEngine engine = ctx->getDiagEngine();94 DiagnosticEngine::HandlerID id = engine.registerHandler(103 DiagnosticEngine::HandlerID id = engine.registerHandler([](Diagnostic &diag) {113 As stated above, the `DiagnosticEngine` holds the core API for diagnostic122 Using the `DiagnosticEngine`, though, is generally not the preferred way to emit254 diagnostic handler with the [`DiagnosticEngine`](#diagnostic-engine).