Author: Alex Zinenko Date: 2021-01-19T13:42:16+01:00 New Revision: 9a60ad216d2fa2e9701849922bfb0db9917f9c93
URL: https://github.com/llvm/llvm-project/commit/9a60ad216d2fa2e9701849922bfb0db9917f9c93 DIFF: https://github.com/llvm/llvm-project/commit/9a60ad216d2fa2e9701849922bfb0db9917f9c93.diff LOG: [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. Added: Modified: mlir/docs/Dialects/LLVM.md Removed: ################################################################################ diff --git a/mlir/docs/Dialects/LLVM.md b/mlir/docs/Dialects/LLVM.md index b396cdebf067..521c5f4c328b 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<T>` 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 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
