Uh oh!
There was an error while loading. Please reload this page.
Implement Swift lowering algorithm in the CoreCLR type system - #99438
Conversation
…s of non-opaque types and to merge opaque intervals
jakobbotsch
left a comment
There was a problem hiding this comment.
LGTM, but you may want to get review from someone more familiar with the VM side.
jkoritzinsky
commented
Mar 8, 2024
I've added a small fix here for the NativeAOT implementation that we discussed offline. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
AaronRobinsonMSFT
left a comment
There was a problem hiding this comment.
I get the statement about contract. I don't think it is all that obvious the contract or expectations here. The 4 count is used in a few places and I replaced one, but aside from the case where byReference = true the split rules aren't clear up front, which is what I normally like to see. As long as the JIT team has clear expectations on their side for the ABI I'm good.
I assume tests will come with the JIT?
Uh oh!
There was an error while loading. Please reload this page.
jkoritzinsky
commented
Mar 11, 2024
Yep the JIT PR will add the test suite. I'll refactor out the max size into a constant. |
This PR finishes out the implementations of the algorithm for RyuJIT-compatible type systems.
This does not update the JIT-EE interface to hook up the new function (@jakobbotsch has already made the JIT-EE change in his branch, so I don't want to conflict with that).