mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-12-15 12:09:51 +00:00
a6cef03f66
This was carry over from LLVM IR where the alias definition can be ambiguous, but MLIR type aliases have no such problems. Having the `type` keyword is superfluous and doesn't add anything. This commit drops it, which also nicely aligns with the syntax for attribute aliases (which doesn't have a keyword). Differential Revision: https://reviews.llvm.org/D125501
29 lines
708 B
MLIR
29 lines
708 B
MLIR
// RUN: mlir-opt -allow-unregistered-dialect %s -split-input-file | FileCheck %s
|
|
|
|
// -----
|
|
// CHECK-LABEL: parseFullySpecified
|
|
// CHECK: !quant.any<i8<-8:7>:f32>
|
|
!qalias = !quant.any<i8<-8:7>:f32>
|
|
func.func @parseFullySpecified() -> !qalias {
|
|
%0 = "foo"() : () -> !qalias
|
|
return %0 : !qalias
|
|
}
|
|
|
|
// -----
|
|
// CHECK-LABEL: parseNoExpressedType
|
|
// CHECK: !quant.any<i8<-8:7>>
|
|
!qalias = !quant.any<i8<-8:7>>
|
|
func.func @parseNoExpressedType() -> !qalias {
|
|
%0 = "foo"() : () -> !qalias
|
|
return %0 : !qalias
|
|
}
|
|
|
|
// -----
|
|
// CHECK-LABEL: parseOnlyStorageType
|
|
// CHECK: !quant.any<i8>
|
|
!qalias = !quant.any<i8>
|
|
func.func @parseOnlyStorageType() -> !qalias {
|
|
%0 = "foo"() : () -> !qalias
|
|
return %0 : !qalias
|
|
}
|