forked from OSchip/llvm-project
aec9e20a3e
Historically, the operations in the MLIR's LLVM dialect only checked that the operand are of LLVM dialect type without more detailed constraints. This was due to LLVM dialect types wrapping LLVM IR types and having clunky verification methods. With the new first-class modeling, it is possible to define type constraints similarly to other dialects and use them to enforce some correctness rules in verifiers instead of having LLVM assert during translation to LLVM IR. This hardening discovered several issues where MLIR was producing LLVM dialect operations that cannot exist in LLVM IR. Depends On D85900 Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D85901 |
||
|---|---|---|
| .. | ||
| func.mlir | ||
| global.mlir | ||
| invalid.mlir | ||
| legalize-for-export.mlir | ||
| nvvm.mlir | ||
| rocdl.mlir | ||
| roundtrip.mlir | ||
| terminator.mlir | ||
| types-invalid.mlir | ||
| types.mlir | ||