Files
swift-mirror/test/DebugInfo/linetable-do.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

46 lines
1.3 KiB
Swift

// RUN: %target-swift-frontend -Xllvm -sil-full-demangle %s -emit-ir -g -o - | %FileCheck %s
// RUN: %target-swift-frontend -Xllvm -sil-full-demangle %s -Xllvm -sil-print-types -emit-sil -emit-verbose-sil -g -o - | %FileCheck --check-prefixes=CHECK-SIL %s
import StdlibUnittest
class Obj {}
func foo (_ a : Int64) throws -> Void {
_blackHole(a)
}
// CHECK-SIL: // main.testDoStmt() throws -> ()
func testDoStmt() throws -> Void {
_blackHole(23)
// CHECK-NOT: !DILocation(line: [[@LINE+1]]
do {
let obj = Obj()
_blackHole(obj)
// The poison debug_value takes the location of the original decl.
try foo(100)
// CHECK-SIL: bb{{.*}}(%{{[0-9]+}} : $()):
// CHECK-SIL-NEXT: strong_release {{.*}}: $Obj{{.*}} line:[[@LINE+1]]:3:cleanup
}
// CHECK-SIL-NEXT: = tuple ()
// CHECK-SIL-NEXT: return {{.*}} line:[[@LINE+1]]
}
try testDoStmt()
// CHECK-SIL: // main.testDoWhileStmt() -> ()
func testDoWhileStmt() -> Void {
// CHECK-NOT: !DILocation(line: [[@LINE+1]]
do {
try foo(100)
// CHECK-SIL: bb{{.*}}(%{{[0-9]+}} : $()):
// CHECK-SIL-NEXT: br [[RETURN_BB:bb[0-9]+]]{{.*}} line:[[@LINE+1]]:3:cleanup
}
// CHECK-SIL: [[RETURN_BB]]:
// CHECK-SIL-NEXT: = tuple ()
// CHECK-SIL-NEXT: return
catch (let e) {
_blackHole(e)
}
}