wasmtime / issue #10248 Tracking issue: Stack switching p... · git-wasmtime · Zulip Chat Archive

Stream: git-wasmtime

Topic: wasmtime / issue #10248 Tracking issue: Stack switching p...

Wasmtime GitHub notifications bot (Feb 19 2025 at 23:13):

frank-emrich opened issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[ ] Support for tags

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

Support for ISAs other than x64

Support for resume.throw instructions (requires exception handling)

Support for deallocating continuations

Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

Windows support

Pulley support

Winch support

Wasmtime GitHub notifications bot (Feb 19 2025 at 23:15):

frank-emrich edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[ ] Support for tags

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Wasmtime GitHub notifications bot (Feb 20 2025 at 12:51):

dhil commented on issue #10248:

Tags are added by PR #10251.

Wasmtime GitHub notifications bot (Feb 20 2025 at 15:39):

alexcrichton added the wasm-proposal:stack-switching label to Issue #10248.

Wasmtime GitHub notifications bot (Feb 20 2025 at 15:48):

alexcrichton edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[ ] Support for tags

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

Wasmtime GitHub notifications bot (Feb 20 2025 at 23:03):

frank-emrich edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

Wasmtime GitHub notifications bot (Feb 26 2025 at 20:10):

fitzgen edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

[ ] Update struct VMContext {...} pseudo-definition comment: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972329164

Wasmtime GitHub notifications bot (Feb 26 2025 at 20:18):

fitzgen edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

[ ] Update struct VMContext {...} pseudo-definition comment: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972329164

[ ] Return an Err(_) if the given function type has results in wasmtime::Tag::new

Wasmtime GitHub notifications bot (Feb 26 2025 at 20:19):

fitzgen edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

[ ] Update struct VMContext {...} pseudo-definition comment: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972329164

[ ] Return an Err(_) if the given function type has results in wasmtime::Tag::new: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972341601

Wasmtime GitHub notifications bot (Feb 26 2025 at 21:16):

fitzgen edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

[ ] Update struct VMContext {...} pseudo-definition comment: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972329164

[ ] Return an Err(_) if the given function type has results in wasmtime::Tag::new: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972341601

[ ] Remove VMTagImport at the vmcontext level: https://github.com/bytecodealliance/wasmtime/pull/10251/files#r1972423938

Wasmtime GitHub notifications bot (Feb 27 2025 at 20:06):

fitzgen edited issue #10248:

This is a tracking issue for the in-progress implementation of the Wasm stack switching proposal. The explainer document for the proposal is here.

Progress of initial implementation

This just tracks what's happening in the sequence of PRs that's providing an initial implementation of the proposal. To get an idea of the extent of the initial implementation, see draft PR #10177.

[x] ~Support for tags~ (implemented in #10251)

[ ] Type definitions for stack switching support

[ ] Runtime support for stack switching

[ ] Compiling stack switching instructions to CLIF

Limitations of initial implementation

These are things that won't be part of the initial implementation:

[ ] Support for ISAs other than x64

[ ] Support for resume.throw instructions (requires exception handling)

[ ] Support for deallocating continuations

[ ] Integration with GC (i.e., allowing continuation references to appear in GC objects, such as arrays an structs)

[ ] Windows support

[ ] Pulley support

[ ] Winch support

Miscellaneous TODO items

[ ] Config::wasm_stack_switching enables both exceptions + stack-switching, but it should only enable stack_switching (from https://github.com/bytecodealliance/wasmtime/pull/10251)

Last updated: Feb 28 2025 at 02:27 UTC