Skip to content

Utility thread and further threading support#279

Merged
yuri91 merged 12 commits intomasterfrom
threading
Feb 26, 2025
Merged

Utility thread and further threading support#279
yuri91 merged 12 commits intomasterfrom
threading

Conversation

@Maqrkk
Copy link
Member

@Maqrkk Maqrkk commented Jan 14, 2025

No description provided.

@Maqrkk Maqrkk force-pushed the threading branch 2 times, most recently from 3312e49 to 8c1098c Compare February 3, 2025 10:38
The size was wrong when booleans were used as thread locals. We now align the thread local area to 8 bytes and calculate the size based on that.
Since there are now 2 places in the code where a new Worker is made, we move the text of the blob into a variable.
This intrinsic will be used in the ThreadLocalLowering pass to bypass a dependency issue with LinearMemoryHelper.
This pass will make it possible to use wasm threadlocals in genericjs, by creating and calling a function in wasm that will calculate the address in memory of the threadlocal.
This secondary threadingObject is introduced because of Closure mode, and to be consistent across the board we use the same method for all module types.
Since the thread setup is asynchronous, we have to create a custom promise to return the module, and only resolve this when the utility thread has been set up.
@yuri91 yuri91 merged commit 530470c into master Feb 26, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants