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

15 lines
636 B
Swift

// REQUIRES: optimized_stdlib
// RUN: %target-swift-frontend -Xllvm -sil-print-types -emit-sil -o /dev/null \
// RUN: %s -Xllvm -sil-print-types -Xllvm -sil-print-debuginfo -Onone -sil-verify-all \
// RUN: -Xllvm -sil-print-types -Xllvm -sil-print-after=diagnostic-constant-propagation \
// RUN: 2>&1 | %FileCheck %s
// CHECK: alloc_stack $any R, loc {{.*}}, scope [[SCOPE:[0-9]+]]
// CHECK-NEXT: init_existential_addr {{.*}} : $*any R, $Float, loc {{.*}}, scope [[SCOPE]]
// CHECK-NEXT: copy_addr [take] %9 to [init] {{.*}} : $*Float, loc {{.*}}, scope [[SCOPE]]
protocol R {}
extension Float: R {}
print(1.0 as Float? as! R)