mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
7cceaff5f3
Type annotations for instruction operands are omitted, e.g. ``` %3 = struct $S(%1, %2) ``` Operand types are redundant anyway and were only used for sanity checking in the SIL parser. But: operand types _are_ printed if the definition of the operand value was not printed yet. This happens: * if the block with the definition appears after the block where the operand's instruction is located * if a block or instruction is printed in isolation, e.g. in a debugger The old behavior can be restored with `-Xllvm -sil-print-types`. This option is added to many existing test files which check for operand types in their check-lines.
28 lines
857 B
Swift
28 lines
857 B
Swift
// RUN: %target-swift-frontend -O -module-name=test -Xllvm -sil-print-types -emit-sil -primary-file %s | %FileCheck %s
|
|
|
|
protocol P { associatedtype A = Int }
|
|
protocol Q : P {}
|
|
|
|
protocol B { var x: Int { get } }
|
|
struct Y<T> {}
|
|
extension Y : B where T : Q { var x: Int { 0 }}
|
|
|
|
extension P {
|
|
var z: Int? { (Y<Self>() as? B)?.x }
|
|
}
|
|
|
|
struct X : Q {
|
|
|
|
// Check that this getter can be folded to a simple "return 0"
|
|
|
|
// CHECK-LABEL: sil hidden @$s4test1XV0A2MeSiSgvg : $@convention(method) (X) -> Optional<Int> {
|
|
// CHECK: bb0(%0 : $X):
|
|
// CHECK-NEXT: debug_value
|
|
// CHECK-NEXT: integer_literal ${{.*}}, 0
|
|
// CHECK-NEXT: struct $Int
|
|
// CHECK-NEXT: %[[ENUM:[0-9]+]] = enum $Optional<Int>, #Optional.some!enumelt
|
|
// CHECK-NEXT: return %[[ENUM]] : $Optional<Int>
|
|
// CHECK-NEXT: } // end sil function '$s4test1XV0A2MeSiSgvg'
|
|
var testMe: Int? { z }
|
|
}
|