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
All the places where NativeAOT emits call <static initialization helper> we should attempt to inline "is it already initialized" quick checks in front of calls (and mark calls as "cold"). I already did it for JIT a while back (#47901) but gave up on it since JIT successfully gets rid of all static initializations with help of Tiered Compilation (and even with single tier) while it's not physically possible for Ahead-of-Time.
All the places where NativeAOT emits call <static initialization helper> we should attempt to inline "is it already initialized" quick checks in front of calls (and mark calls as "cold"). I already did it for JIT a while back (#47901) but gave up on it since JIT successfully gets rid of all static initializations with help of Tiered Compilation (and even with single tier) while it's not physically possible for Ahead-of-Time.
All the places where NativeAOT emits
call <static initialization helper>
we should attempt to inline "is it already initialized" quick checks in front of calls (and mark calls as "cold"). I already did it for JIT a while back (#47901) but gave up on it since JIT successfully gets rid of all static initializations with help of Tiered Compilation (and even with single tier) while it's not physically possible for Ahead-of-Time.Tracking issue for #64242
The text was updated successfully, but these errors were encountered: