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
Right now we suspend the runtime when updating the active IL version. I believe this was only required for jumpstamps, since we had to stop the runtime to make sure no threads were going to have a race in executing the prolog of a jitted method. dotnet/coreclr#26740 makes it so ReJIT no longer uses jumpstamps, it should be safe to stop suspending the runtime.
The text was updated successfully, but these errors were encountered:
Right now we suspend the runtime when updating the active IL version. I believe this was only required for jumpstamps, since we had to stop the runtime to make sure no threads were going to have a race in executing the prolog of a jitted method. dotnet/coreclr#26740 makes it so ReJIT no longer uses jumpstamps, it should be safe to stop suspending the runtime.
The text was updated successfully, but these errors were encountered: