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

21 lines
873 B
Swift

// RUN: %target-swift-frontend -Xllvm -sil-print-types -emit-sil -enable-experimental-concurrency -target %target-swift-5.1-abi-triple %s | %FileCheck %s
// REQUIRES: concurrency
// REQUIRES: swift_in_compiler
@_transparent
func reasyncFunction(_ value: Optional<Int>, _ fn: () async throws -> Int) reasync rethrows -> Int {
switch value {
case .some(let x): return x
case .none: return try await fn()
}
}
// CHECK-LABEL: sil hidden @$s26mandatory_inlining_reasync20callsReasyncFunctionSiyF : $@convention(thin) () -> Int {
// CHECK: [[FN:%.*]] = function_ref @$s26mandatory_inlining_reasync20callsReasyncFunctionSiyFSiyXEfU_ : $@convention(thin) () -> Int
// CHECK-NEXT: [[RESULT:%.*]] = apply [[FN]]() : $@convention(thin) () -> Int
// CHECK-NEXT: return [[RESULT]] : $Int
func callsReasyncFunction() -> Int {
return reasyncFunction(nil, { return 321 } )
}