mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
7cceaff5f3
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.
20 lines
1020 B
Swift
20 lines
1020 B
Swift
// RUN: %target-swift-frontend -enable-experimental-static-assert -Xllvm -sil-print-types -emit-silgen %s | %FileCheck %s
|
|
|
|
// CHECK-LABEL: sil hidden [ossa] @$s12pound_assert15noCustomMessage{{[_0-9a-zA-Z]*}}
|
|
func noCustomMessage() {
|
|
#assert(true)
|
|
// CHECK: [[LOGIC_VALUE:%.*]] = struct_extract {{.*}}
|
|
// CHECK-NEXT: [[MESSAGE:%.*]] = string_literal utf8 ""
|
|
// CHECK-NEXT: builtin "poundAssert"([[LOGIC_VALUE]] : $Builtin.Int1, [[MESSAGE]] : $Builtin.RawPointer)
|
|
}
|
|
// CHECK: } // end sil function '$s12pound_assert15noCustomMessage{{[_0-9a-zA-Z]*}}'
|
|
|
|
// CHECK-LABEL: sil hidden [ossa] @$s12pound_assert13customMessage{{[_0-9a-zA-Z]*}}
|
|
func customMessage() {
|
|
#assert(true, "custom message")
|
|
// CHECK: [[LOGIC_VALUE:%.*]] = struct_extract {{.*}}
|
|
// CHECK-NEXT: [[MESSAGE:%.*]] = string_literal utf8 "custom message"
|
|
// CHECK-NEXT: builtin "poundAssert"([[LOGIC_VALUE]] : $Builtin.Int1, [[MESSAGE]] : $Builtin.RawPointer)
|
|
}
|
|
// CHECK: } // end sil function '$s12pound_assert13customMessage{{[_0-9a-zA-Z]*}}'
|