You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AnnaZaksmannequin opened this issue
Jan 8, 2018
· 4 comments
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfLinuxPlatform: LinuxruntimeThe Swift Runtime
There are various places in the metadata generation where NULL values are being injected simply because there’s some objective-c related field that isn’t important on a non-objc platform. We should remove these and make sure that things still work. (Note that the debugger wants to preserve some sort of magic number that can be used to identify classes. On ObjC platforms the debugger uses the Swift class's ObjC data to do that.)
The text was updated successfully, but these errors were encountered:
Reminded of this again today. I don't think it would be too difficult, so maybe a good task to assign to someone who's already familiar with the compiler a bit and wants to dive into IRGen and the runtime?
As for a "magic number to identify classes", the value witness table for every class is the same (since it's "just" for native-object references), so we can probably use that: $sBoWV
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfLinuxPlatform: LinuxruntimeThe Swift Runtime
Additional Detail from JIRA
md5: 1801085f2cc5dfb398494cbf214ff76d
Issue Description:
There are various places in the metadata generation where NULL values are being injected simply because there’s some objective-c related field that isn’t important on a non-objc platform. We should remove these and make sure that things still work. (Note that the debugger wants to preserve some sort of magic number that can be used to identify classes. On ObjC platforms the debugger uses the Swift class's ObjC data to do that.)
The text was updated successfully, but these errors were encountered: