mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
fcbebc51c7
This commit also changes how specialized types are being emitted. Previously we would not emitthe detailed member information in the specialized type itself, and instead rely on the fact that it was present in the unspecialized type, however, this wold prevent us from emitting any bound generic members, so we're now emitting the members in both variants of the type. This uncovered a with type aliases that this commit also addresses: Because we don't canonicalize types prior to caching in order to preserve type sugar, alternative representations of recursive types (with one or more levels of recursion unfolded) could create potential infinite chains of types. This is addressed by checking whether a sugared type has an already emitted canonical representation first, and if yes, creating a typedef node pointing directly to it. The donwside of doing this is that it can lead to the disappearnce of type aliases definitions when they are used as parameters in bound generic types. However, we still preserve that a type was `MyClass<MyAlias>`. We just might have a typedef pointing director from `MyClass<MyAlias>` -> `MyClass<CanonicalType>`. rdar://144315592
16 lines
565 B
Swift
16 lines
565 B
Swift
// RUN: %target-swift-frontend -primary-file %s -emit-ir -gdwarf-types -o - | %FileCheck %s
|
|
|
|
class SomeClass {
|
|
let first = 4
|
|
let second = "Hello"
|
|
}
|
|
|
|
// CHECK: !DICompositeType(tag: DW_TAG_structure_type, name: "SomeClass",
|
|
// CHECK-SAME: size: {{64|32}}, elements:
|
|
// CHECK-SAME: runtimeLang: DW_LANG_Swift,{{.*}} identifier: "$s7classes9SomeClassCD")
|
|
|
|
// CHECK: !DIDerivedType(tag: DW_TAG_member, name: "first",
|
|
// CHECK-SAME: size: {{64|32}})
|
|
// CHECK: !DIDerivedType(tag: DW_TAG_member, name: "second",
|
|
// CHECK-SAME: size: {{128|96}}, offset: {{64|32}})
|