-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIT: fix bug introduced by recent throw helper block changes #93897
Conversation
`compUsesThrowHelper` indicates codegen will likely need to create a call to a helper, whether or not such calls are shared. In dotnet#93371 I didn't appreciate this, and so the JIT was failing to set `compUsesThrowHelper` in cases where a throw helper was going to be needed but throw helper calls were not going to be shared. Fixes dotnet#93710.
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Details
In #93371 I didn't appreciate this, and so the JIT was failing to set Fixes #93710.
|
FYI @dotnet/jit-contrib |
/azp run runtime-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
Outlerloop was green. |
…93897) `compUsesThrowHelper` indicates codegen will likely need to create a call to a helper, whether or not such calls are shared. In dotnet#93371 I didn't appreciate this, and so the JIT was failing to set `compUsesThrowHelper` in cases where a throw helper was going to be needed but throw helper calls were not going to be shared. Fixes dotnet#93710.
compUsesThrowHelper
indicates codegen will likely need to create a call to a helper, whether or not such calls are shared.In #93371 I didn't appreciate this, and so the JIT was failing to set
compUsesThrowHelper
in cases where a throw helper was going to be needed but throw helper calls were not going to be shared.Fixes #93710.