Thanks to visit codestin.com
Credit goes to github.com

Skip to content

wasm-mt: Fix Environment.ProcessorCount ILLink substitution to 1 #106384

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

Merged
merged 1 commit into from
Aug 14, 2024

Conversation

akoeplinger
Copy link
Member

On multi-threaded wasm we shouldn't be hardcoding the processor count to 1, we can rely on the runtime to report the correct value.

On multi-threaded wasm we shouldn't be hardcoding the processor count to 1, we can rely on the runtime to report the correct value.
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Aug 14, 2024
@akoeplinger akoeplinger added area-Build-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Aug 14, 2024
@pavelsavara pavelsavara merged commit b500820 into dotnet:main Aug 14, 2024
70 checks passed
@akoeplinger akoeplinger deleted the fix-wasm-mt-processorcount branch August 14, 2024 12:51
@github-actions github-actions bot locked and limited conversation to collaborators Sep 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants