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 the implementation of the Swift frozen struct lowering in Mono runtime. The Swift runtime enregisters frozen structs as a set of primitives if the sequence <= 4 machine words. The Mono runtime should utilize the lowering API and implements the same behavior as the Swift runtime when interoperating with Swift in JIT/AOT and interpreter configurations.
The lowering algorithm is implemented in . The Mono runtime should utilize the lowering API and have the same behavior as Swift runtime when interop with Swift in JIT/AOT and interpreter configurations.
The existing runtime tests should be used for validation.
(optional) Add cache that maps structs to computed lowering (SwiftPhysicalLowering). The goal is to eliminate repeated runs of lowering algorithm for "known" structs.
The text was updated successfully, but these errors were encountered:
(optional) Add cache that maps structs to computed lowering (SwiftPhysicalLowering). The goal is to eliminate repeated runs of lowering algorithm for "known" structs.
Description
This issue tracks the implementation of the Swift frozen struct lowering in Mono runtime. The Swift runtime enregisters frozen structs as a set of primitives if the sequence <= 4 machine words. The Mono runtime should utilize the lowering API and implements the same behavior as the Swift runtime when interoperating with Swift in JIT/AOT and interpreter configurations.
The lowering algorithm is implemented in . The Mono runtime should utilize the lowering API and have the same behavior as Swift runtime when interop with Swift in JIT/AOT and interpreter configurations.
The existing runtime tests should be used for validation.
Tasks
SwiftPhysicalLowering
). The goal is to eliminate repeated runs of lowering algorithm for "known" structs.The text was updated successfully, but these errors were encountered: