Skip to content

Commit

Permalink
[mlir] Clarify docs around LLVM dialect-compatible types
Browse files Browse the repository at this point in the history
Explicitly mention that there is exactly one MLIR type that corresponds
to a given LLVM IR type.
  • Loading branch information
ftynse committed Jan 19, 2021
1 parent 2c4f6be commit 9a60ad2
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions mlir/docs/Dialects/LLVM.md
Expand Up @@ -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
Expand Down

0 comments on commit 9a60ad2

Please sign in to comment.