Files
swift-mirror/test/SILOptimizer/sil_combine_opaque.sil
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

26 lines
1.0 KiB
Plaintext

// RUN: %target-sil-opt -sil-print-types -enable-sil-opaque-values -enable-sil-verify-all -sil-combine %s | %FileCheck %s
struct S<T> {
var t : T
}
// Test SIL combine's handling of retain_value/release_value.
//
// CHECK-LABEL: sil @testSpecializeOpaque : $@convention(thin) <T> (@in S<T>) -> () {
// CHECK-LABEL: bb0(%0 : $S<T>):
// CHECK: retain_value %0 : $S<T>
// CHECK: [[F:%.*]] = function_ref @testSpecializeOpaque : $@convention(thin) <τ_0_0> (@in S<τ_0_0>) -> ()
// CHECK: [[CALL:%.*]] = apply [[F]]<T>(%0) : $@convention(thin) <τ_0_0> (@in S<τ_0_0>) -> ()
// CHECK: release_value %0 : $S<T>
// CHECK: return %{{.*}} : $()
// CHECK-LABEL: } // end sil function 'testSpecializeOpaque'
sil @testSpecializeOpaque : $@convention(thin) <T> (@in S<T>) -> () {
bb0(%0 : $S<T>):
retain_value %0 : $S<T>
%f = function_ref @testSpecializeOpaque : $@convention(thin) <T> (@in S<T>) -> ()
%call = apply %f<T>(%0) : $@convention(thin) <τ_0_0> (@in S<τ_0_0>) -> ()
release_value %0 : $S<T>
%999 = tuple ()
return %999 : $()
}