Uh oh!
There was an error while loading. Please reload this page.
[wasm] Enable SIMD - #80797
Conversation
Co-authored-by: Ankit Jain <radical@gmail.com>
radekdoulik
commented
Jan 19, 2023
Currently we fail on helix because v8 is too old. I am trying to improve that with 2 independent approaches, #80808 and dotnet/dotnet-buildtools-prereqs-docker#774 |
.. instead crashing with an exception like: ``` src/mono/wasm/build/WasmApp.Native.targets(296,5): error MSB4018: (NETCORE_ENGINEERING_TELEMETRY=Build) The "ManagedToNativeGenerator" task failed unexpectedly. System.BadImageFormatException: This PE image is not a managed executable. at System.Reflection.MetadataLoadContext.LoadFromStreamCore(Stream peStream) at System.Reflection.MetadataLoadContext.LoadFromAssemblyPath(String assemblyPath) at PInvokeTableGenerator.Generate(String[] pinvokeModules, String[] assemblies, String outputPath) in /_/src/tasks/WasmAppBuilder/PInvokeTableGenerator.cs:line 42 at ManagedToNativeGenerator.ExecuteInternal() in /_/src/tasks/WasmAppBuilder/ManagedToNativeGenerator.cs:line 68 at ManagedToNativeGenerator.Execute() in /_/src/tasks/WasmAppBuilder/ManagedToNativeGenerator.cs:line 53 at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) ``` The wasm targets currently are not able to differentiate the managed assemblies from the unmanaged ones. so it needs to be handled here.
…leSIMD=true Instead, let the property be effective only for the AOT case.
…move v8 config as that isn't supported
…runtime into pr-wasm-enable-simd
radical
commented
Jan 20, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Also remove --experimental-wasm-simd option, which shouldn't be needed for newer v8
As we need newer v8
ghost
commented
Jan 20, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsLet see how it goes on CI
|
The correlation payload is read only
This reverts commit a15b3ef.
Let see whether it will avoid all the writes to correlation payload path
To try if we can use newer node in path
|
Azure Pipelines successfully started running 1 pipeline(s). |
lewing
left a comment
There was a problem hiding this comment.
LGTM but we need to resolve the wbt failure
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
radical
commented
Feb 27, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radekdoulik
commented
Feb 27, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radekdoulik
commented
Feb 27, 2023
The |
lewing
commented
Mar 1, 2023
@maraf are you looking into this? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
kg
left a comment
There was a problem hiding this comment.
Looks good, with the caveat that I don't have the ability to fully vet the yml or msbuild bits (but the latter do look correct to me), and I left some comments
Change default value of
WasmEnableSIMDproperty to true. That enables SIMD for wasm/AOT.Use docker image with newer v8 and node on helix.