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
This issue tracks implementation progress of UnmanagedCallersOnly for the Swift calling convention. When a Swift function calls into .NET, it utilizes the swiftself and swifterror registers to pass context pointers according to the calling convention. In methods annotated with the UnmanagedCallersOnly attribute, users can add SwiftSelf argument to load swiftself register value. Additionally, users can add SwiftError argument to store an exception pointer into swifterror register.
The existing runtime tests should be used for verification.
Note: The default configuration on Apple and Apple mobile platforms uses the LLVM backend, but native wrappers are compiled with the mini backend. Efforts to enable LLVM compilation of native wrappers has been done in #96910.
The text was updated successfully, but these errors were encountered:
Description
This issue tracks implementation progress of UnmanagedCallersOnly for the Swift calling convention. When a Swift function calls into .NET, it utilizes the
swiftself
andswifterror
registers to pass context pointers according to the calling convention. In methods annotated with theUnmanagedCallersOnly
attribute, users can addSwiftSelf
argument to loadswiftself
register value. Additionally, users can addSwiftError
argument to store an exception pointer intoswifterror
register.The existing runtime tests should be used for verification.
Tasks
Note: The default configuration on Apple and Apple mobile platforms uses the LLVM backend, but native wrappers are compiled with the mini backend. Efforts to enable LLVM compilation of native wrappers has been done in #96910.
The text was updated successfully, but these errors were encountered: