From 9a60ad216d2fa2e9701849922bfb0db9917f9c93 Mon Sep 17 00:00:00 2001 From: Alex Zinenko Date: Tue, 19 Jan 2021 13:42:16 +0100 Subject: [PATCH] [mlir] Clarify docs around LLVM dialect-compatible types Explicitly mention that there is exactly one MLIR type that corresponds to a given LLVM IR type. --- mlir/docs/Dialects/LLVM.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/mlir/docs/Dialects/LLVM.md b/mlir/docs/Dialects/LLVM.md index b396cde..521c5f4 100644 --- a/mlir/docs/Dialects/LLVM.md +++ b/mlir/docs/Dialects/LLVM.md @@ -224,6 +224,11 @@ compatible. For example, signed and unsigned integers are not compatible. LLVM provides a function, `bool LLVM::isCompatibleType(Type)`, that can be used as a compatibility check. +Each LLVM IR type corresponds to *exactly one* MLIR type, either built-in or +LLVM dialect type. For example, because `i32` is LLVM-compatible, there is no +`!llvm.i32` type. However, `!llvm.ptr` is defined in the LLVM dialect as +there is no corresponding built-in type. + ### Additional Simple Types The following non-parametric types derived from the LLVM IR are available in the -- 2.7.4