mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
ba68faaed5
Find all the usages of `--enable-experimental-feature` or `--enable-upcoming-feature` in the tests and replace some of the `REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which should correctly apply to depending on the asserts/noasserts mode of the toolchain for each feature. Remove some comments that talked about enabling asserts since they don't apply anymore (but I might had miss some). All this was done with an automated script, so some formatting weirdness might happen, but I hope I fixed most of those. There might be some tests that were `REQUIRES: asserts` that might run in `noasserts` toolchains now. This will normally be because their feature went from experimental to upcoming/base and the tests were not updated.
35 lines
932 B
Swift
35 lines
932 B
Swift
// RUN: %target-swift-frontend -target armv7-apple-none-macho -Xcc -D__MACH__ -emit-ir %s -enable-experimental-feature Embedded | %FileCheck %s
|
|
// RUN: %target-swift-frontend -target arm64-apple-none-macho -Xcc -D__MACH__ -Xcc -D__arm64__ -Xcc -D__APPLE__ -emit-ir %s -enable-experimental-feature Embedded | %FileCheck %s
|
|
|
|
// REQUIRES: swift_in_compiler
|
|
// REQUIRES: optimized_stdlib
|
|
// REQUIRES: CODEGENERATOR=ARM
|
|
// REQUIRES: embedded_stdlib_cross_compiling
|
|
// REQUIRES: swift_feature_Embedded
|
|
|
|
// https://github.com/apple/swift/issues/73249
|
|
// UNSUPPORTED: OS=windows-msvc
|
|
|
|
protocol MyOptionSet: Equatable {
|
|
init(rawValue: Int)
|
|
init()
|
|
}
|
|
|
|
extension MyOptionSet {
|
|
var isEmpty: Bool {
|
|
return self == Self()
|
|
}
|
|
init() {
|
|
self.init(rawValue: 0)
|
|
}
|
|
}
|
|
|
|
struct ShippingOptions: MyOptionSet {
|
|
let rawValue: Int
|
|
}
|
|
|
|
var s = ShippingOptions(rawValue: 42)
|
|
print(s.isEmpty)
|
|
|
|
// CHECK: define {{.*}}i32 @main(i32 %0, ptr %1)
|