Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[coop-threading] Track concurrent state for synchronous calls#12123

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
TartanLlama wants to merge21 commits intobytecodealliance:main
base:main
Choose a base branch
Loading
fromTartanLlama:sy/sync-multithreading

Conversation

@TartanLlama
Copy link
Contributor

@TartanLlamaTartanLlama commentedDec 4, 2025
edited
Loading

Threads are currently not created on sync->sync export calls, sync host->guest calls, and module-level start function calls. This PR adds support to this for all of these.

I added a component-model-async feature to wasmtime-environ so that sync->sync adapters are compiled as they were originally for wasip2 code, avoiding changing performance characteristics.

Rather than use the existing prepare_call + start_call machinery, I introduced sync_to_sync_enter/exit_call intrinsics to avoid adding additional host frames to the stack for sync calls.

Currently, doing operations that require thread state insidepost_return functions is unsupported. If we're happy merging this as-is and creating an issue to resolve this later, we can do so, or I can try and address it prior to merging.

Fixes#11954

@github-actionsgithub-actionsbot added the wasmtime:apiRelated to the API of the `wasmtime` crate itself labelDec 4, 2025
@alexcrichtonalexcrichton moved this fromBacklog toIn progress inShip WASIp3Dec 8, 2025
@TartanLlamaTartanLlama marked this pull request as ready for reviewDecember 11, 2025 15:05
@TartanLlamaTartanLlama requested review froma team ascode ownersDecember 11, 2025 15:05
@TartanLlamaTartanLlama requested review fromabrown and removed request fora teamDecember 11, 2025 15:05
@TartanLlamaTartanLlama requested review frompchickey and removed request fora teamDecember 11, 2025 15:05
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@abrownabrownAwaiting requested review from abrownabrown is a code owner automatically assigned from bytecodealliance/wasmtime-compiler-reviewers

@pchickeypchickeyAwaiting requested review from pchickeypchickey is a code owner automatically assigned from bytecodealliance/wasmtime-core-reviewers

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

wasmtime:apiRelated to the API of the `wasmtime` crate itself

Projects

Status: In progress

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

resources.wast test failing in sync mode with cooperative multithreading

1 participant

@TartanLlama

[8]ページ先頭

©2009-2025 Movatter.jp