Spill side effects before impStoreNullableFields #105529
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #105518
The root cause of the issue is the IR like this:
since that call demands a ret-buffer (to return System.Decimal) on Windows, we have to spill it right in the importer. @jakobbotsch pointed me to
impStoreStruct
helper that takes care about ABI for such stores.This led to an assert in LowerStructCall in Checked and to an invalid program exception in Release in EF. I've validated that this fix fixes the EF repro.
It's a bit unfortunate that we have to care about codegen-level things like ABI handling that early, but 🤷