Files
swift-mirror/test/SILOptimizer/mandatory_inlining_devirt_multifile.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
738 B
Swift

// RUN: %target-swift-frontend -module-name test -primary-file %s %S/Inputs/mandatory_inlining_devirt_other.swift -Xllvm -sil-print-types -emit-sil -o - | %FileCheck %s
// rdar://45110471
// We only generate SIL v-tables for these two classes in this file, but
// class hierarchy analysis needs to walk through the third class in the
// helper file.
class Base {
fileprivate func foo() { print("base") }
func callit() { foo() }
}
class Derived : Middle {
fileprivate override func foo() { print("derived") }
}
// CHECK-LABEL: sil hidden @$s4test4BaseC6callityyF
// CHECK: [[T0:%.*]] = class_method %0 : $Base, #Base.foo
// CHECK-NEXT: apply [[T0]](%0)
// CHECK-LABEL: } // end sil function '$s4test4BaseC6callityyF'