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

31 lines
1015 B
Swift

// RUN: %target-swift-frontend -parse-as-library -O -Xllvm -sil-print-types -emit-sil %s | %FileCheck %s
// REQUIRES: swift_stdlib_no_asserts,optimized_stdlib,CPU=x86_64
// This is an end-to-end test to ensure that the optimizer can propagate
// resilient enum cases (FloatingPointRoundingRule) and produces optimal
// code for Float.rounded().
// CHECK-LABEL: sil @{{.*}}propagate_roundingmode
// CHECK: bb0:
// CHECK-NEXT: %0 = integer_literal {{.*}}, 0
// CHECK-NEXT: %1 = struct $Int (%0 {{.*}})
// CHECK-NEXT: return %1
public func propagate_roundingmode() -> Int {
let rm = FloatingPointRoundingRule.toNearestOrEven
switch rm {
case .toNearestOrAwayFromZero:
return 1
default:
return 0
}
}
// CHECK-LABEL: sil @{{.*}}round_floating_point
// CHECK: bb0({{.*}}):
// CHECK: [[R:%[0-9]+]] = builtin "int_round{{.*}}"
// CHECK: [[F:%[0-9]+]] = struct $Float ([[R]]
// CHECK: return [[F]]
public func round_floating_point(_ x: Float) -> Float {
return x.rounded()
}