-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[browser][mt] Unify multithreading switches #97560
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsWe used to have a runtime build switch:
This PR removes
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Looks good to me 👍
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
This has likely broken wasm perf builds - https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2370299/logs/282 . |
It seems like this also broke WBT for me locally:
|
We used to have a runtime build switch:
/p:MonoWasmBuildVariant=multithread
and a public propertyWasmEnableThreads
. When running library tests it was required to pass both switches, otherwise we got an error:This PR removes
MonoWasmBuildVariant
and replaces it withWasmEnableThreads
that will be used for runtime build and running mt-based apps / lib tests.Rename
FEATURE_WASM_THREADS
->FEATURE_WASM_MANAGED_THREADS
,FeatureWasmThreads
->FeatureWasmManagedThreads
. RemovingMonoWasmThreads
.