Files
swift-mirror/test/SILOptimizer/cast_folding_conditional_conformance.swift
Erik Eckstein 7cceaff5f3 SIL: don't print operand types in textual SIL
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.
2024-11-21 18:49:52 +01:00

23 lines
845 B
Swift

// RUN: %target-swift-frontend %s -Xllvm -sil-print-types -emit-sil -O -o - | %FileCheck %s
// RUN: %target-swift-frontend %s -emit-ir -o /dev/null
// rdar://problem/38694450
protocol P {}
extension Array: P where Element: P {}
struct X {}
// CHECK-LABEL: sil @$s36cast_folding_conditional_conformance5arrayyyF : $@convention(thin) () -> () {
public func array() {
// CHECK: unconditional_checked_cast_addr Array<X> in {{%[0-9]*}} : $*Array<X> to any P in {{%[0-9]*}} : $*any P
var x = [X()] as! P
}
struct Y<T> {}
extension Y: P where T: P {}
// CHECK-LABEL: sil @$s36cast_folding_conditional_conformance3fooyyxmlF : $@convention(thin) <T> (@thick T.Type) -> () {
public func foo<T>(_: T.Type) {
// CHECK: unconditional_checked_cast_addr Y<T> in {{%[0-9]*}} : $*Y<T> to any P in {{%[0-9]*}} : $*any P
var x = Y<T>() as! P
}