-
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
[wasm] Don't allocate jiterpreter AOT tables unless AOT was enabled at build time #90978
Conversation
If RunAOTCompilation was not set according to config, don't allocate tables for jiterpreter AOT optimizations
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis PR flows the RunAOTCompilation MSBuild property through into the boot config, and only allocates the jiterpreter's AOT tables at startup if the property was set at build time.
|
src/tasks/Microsoft.NET.Sdk.WebAssembly.Pack.Tasks/GenerateWasmBootJson.cs
Outdated
Show resolved
Hide resolved
Cleanup
@@ -409,6 +409,8 @@ | |||
<_CmakeEnvironmentVariable Include="WASM_ENABLE_SIMD=0" Condition="'$(WasmEnableSIMD)' == 'false'" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@radical @radekdoulik Why do we have these conditions here? We never build runtime with these settings, aren't we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be my mistake ...
This PR flows the RunAOTCompilation MSBuild property through into the boot config, and only allocates the jiterpreter's AOT tables at startup if the property was set at build time.
This should reduce the startup penalty from pre-allocating function table entries for non-AOT scenarios.
Related dotnet/aspnetcore#49909