Files
swift-mirror/test/IRGen/prespecialized-metadata/struct-inmodule-0argument.swift
Alex Lorenz 4858cb6225 [IRGen][interop] do not add 'nocapture' to not bitwise takable types
The use of 'nocapture' for parameters and return values is incorrect for C++ types, as they can actually capture a pointer into its own value (e.g. std::string in libstdc++)

rdar://115062687
2023-09-25 17:43:34 -07:00

40 lines
1.0 KiB
Swift

// RUN: %swift -prespecialize-generic-metadata -target %module-target-future -emit-ir %s | %FileCheck %s -DINT=i%target-ptrsize -DALIGNMENT=%target-alignment
// REQUIRES: VENDOR=apple || OS=linux-gnu
// UNSUPPORTED: CPU=i386 && OS=ios
// UNSUPPORTED: CPU=armv7 && OS=ios
// UNSUPPORTED: CPU=armv7s && OS=ios
struct Value {
let first: Int
}
@inline(never)
func consume<T>(_ t: T) {
withExtendedLifetime(t) { t in
}
}
// CHECK: define hidden swiftcc void @"$s4main4doityyF"() #{{[0-9]+}} {
// CHECK: call swiftcc void @"$s4main7consumeyyxlF"(
// CHECK-SAME: ptr noalias %{{[0-9]+}},
// CHECK-SAME: ptr getelementptr inbounds (
// CHECK-SAME: <{
// CHECK-SAME: ptr,
// CHECK-SAME: ptr,
// CHECK-SAME: [[INT]],
// CHECK-SAME: ptr,
// CHECK-SAME: i32
// CHECK-SAME: i64
// CHECK-SAME: }>,
// CHECK-SAME: ptr @"$s4main5ValueVMf",
// CHECK-SAME: i32 0,
// CHECK-SAME: i32 2
// CHECK-SAME: )
// CHECK-SAME: )
// CHECK: }
func doit() {
consume( Value(first: 13) )
}
doit()