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.
36 lines
827 B
Swift
36 lines
827 B
Swift
// RUN: %target-swift-emit-ir %s -parse-stdlib -module-name Swift -enable-experimental-feature Embedded -wmo -target arm64e-apple-none | %FileCheck %s
|
|
|
|
// REQUIRES: swift_in_compiler
|
|
// REQUIRES: swift_feature_Embedded
|
|
|
|
class MyClass {}
|
|
|
|
struct MyStruct {
|
|
var c: MyClass
|
|
}
|
|
|
|
public func foo() -> Builtin.Int1 {
|
|
return Builtin.ispod(MyStruct.self)
|
|
}
|
|
|
|
// CHECK: define {{.*}}i1 @"$ss3fooBi1_yF"()
|
|
// CHECK-NEXT: entry:
|
|
// CHECK-NEXT: ret i1 false
|
|
// CHECK-NEXT: }
|
|
|
|
public func bar() -> Builtin.Int1 {
|
|
var s = MyGenericStruct<MyStruct>()
|
|
return s.foo()
|
|
}
|
|
|
|
public struct MyGenericStruct<T> {
|
|
public func foo() -> Builtin.Int1 {
|
|
return Builtin.ispod(T.self)
|
|
}
|
|
}
|
|
|
|
// CHECK: define {{.*}}i1 @"$ss15MyGenericStructV3fooBi1_yFs0aC0V_Tg5"()
|
|
// CHECK-NEXT: entry:
|
|
// CHECK-NEXT: ret i1 false
|
|
// CHECK-NEXT: }
|