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
{{ message }}
Repository navigation
Revisit EH at P/Invoke boundary for QCalls #123482
we don't push them on pinvoke boundary for perf reason (@jkotas believed the perf hit would not be acceptable
On Unix, we would have to get rid of the internal EH interop for QCalls to do this correctly: catch the exception on QCall unmanaged side, store it in a thread local variable or in an [out] argument register, and rethrow it on the managed size.
Also, we would have the do something about the other managed->unmanaged transitions that do not go through the regular PInvoke path. For the less perf-sensitive transitions like ThePreStub, it should be ok to push the callee saved float registers.
Activity
MihuBot commentedon Jan 22, 2026
I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):
[-]Revisit EH at P/Invoke boundary[/-][+]Revisit EH at P/Invoke boundary for QCalls[/+]dotnet-policy-service commentedon Apr 15, 2026
Tagging subscribers to this area: @agocke
See info in area-owners.md if you want to be subscribed.
Route QCall exceptions through marshalling (#132420)
jkotas commentedon Oct 6, 2026
This was fixed by #132420