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

22 lines
739 B
Swift

// RUN: %target-swift-frontend %s -O -Xllvm -sil-print-types -emit-sil | %FileCheck %s -check-prefix=CHECK-O
// RUN: %target-swift-frontend %s -Osize -Xllvm -sil-print-types -emit-sil | %FileCheck %s -check-prefix=CHECK-OSIZE
@_semantics("optimize.sil.specialize.generic.size.never")
func foo<T>(_ t: T) -> T {
return t
}
// CHECK-O-LABEL: sil @{{.*}}test
// CHECK-O: %[[LITERAL:.+]] = integer_literal $Builtin.Int{{[0-9]+}}, 27
// CHECK-O: %[[STRUCT:.+]] = struct $Int (%[[LITERAL]] : $Builtin.Int{{[0-9]+}})
// CHECK-O: return %[[STRUCT]]
// CHECK-OSIZE-LABEL: sil {{.*}} @{{.*}}foo
// CHECK-OSIZE-LABEL: sil @{{.*}}test
// CHECK-OSIZE: function_ref {{.*}}foo
// CHECK-OSIZE: apply
public func test() -> Int {
return foo(27)
}