[browser] Fix SIMD+EH check

[maraf]

• Before this change the linkerWasmEnableSIMD and linkerWasmEnableEH used in configureRuntimeStartup to check support for these features always had the default (true) value. Throwing assert error even when SIMD and EH was disabled for build.
• Call cwraps.mono_wasm_abort from runtimeHelpers.abort only after cwraps are ready (onRuntimeInitializedAsync).

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

• Before this change the linkerWasmEnableSIMD and linkerWasmEnableEH used in configureRuntimeStartup to check support for these features always had the default (true) value. Throwing assert error even when SIMD and EH was disabled for build.
• Call cwraps.mono_wasm_abort from runtimeHelpers.abort only after cwraps are ready (onRuntimeInitializedAsync).

Author:	maraf
Assignees:	maraf
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript, os-browser
Milestone:	9.0.0

[radical]

Before this change the linkerWasmEnableSIMD and linkerWasmEnableEH used in configureRuntimeStartup to check support for these features always had the default (true) value. Throwing assert error even when SIMD and EH was disabled for build.

So, this always failed on browsers that didn't support SIMD/EH, even when SIMD was disabled in the build? Can we test this with chrome/v8?

[maraf]

So, this always failed on browsers that didn't support SIMD/EH, even when SIMD was disabled in the build?

Exactly.

Can we test this with chrome/v8?

If we install Chrome 85 or Firefox 88, we can test it. I can look into it in a separate PR.

[lewing]

/backport to release/8.0

[github-actions]

Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/6265063819

[lewing]

/backport to release/8.0-rc2

[github-actions]

Started backporting to release/8.0-rc2: https://github.com/dotnet/runtime/actions/runs/6267696867

[lewing]

closed in favor of #92439