T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Slides for Wasmtime meeting on 2022-05-12 (#4149)

Browse Source
This commit is contained in:
Andrew Brown
2022-05-12 10:50:55 -07:00
committed by GitHub
parent 42873111b0
commit 2111f7dba8
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
meetings/wasmtime/2022/wasmtime-05-12-slides.pdf Normal file
View File

Binary file not shown.

4
meetings/wasmtime/2022/wasmtime-05-12.md
View File

@@ -54,14 +54,14 @@
- Dan: sounds right, TLS thing can be done in Rust async eventually. - Dan: sounds right, TLS thing can be done in Rust async eventually.
Question is transitional plan Question is transitional plan
- Dan: maybe this means we have a bit higher tolerance for now for temporary - Dan: maybe this means we have a bit higher tolerance for now for temporary
workarounds workarounds
- Andrew: what does the async timeline look like? - Andrew: what does the async timeline look like?
- Alex: working on it, lots of spec work, still a bit unsure - Alex: working on it, lots of spec work, still a bit unsure
- Dan: recently started working on a "preview 2" snapshot of WASI, based on - Dan: recently started working on a "preview 2" snapshot of WASI, based on
some new async stuff; timeline is months some new async stuff; timeline is months
2. Shared memory implementation (i.e., changes to `VMContext`) 2. Shared memory implementation (i.e., changes to `VMContext`)
- Andrew: slides - Andrew: [slides](wasmtime-05-12-slides.pdf)
- Andrew: working on shared memory in Wasmtime, help from Alex. - Andrew: working on shared memory in Wasmtime, help from Alex.
- Andrew: main problem is how to share `current_length` in - Andrew: main problem is how to share `current_length` in
`VMMemoryDefinition`, which has a separate copy in each instance `VMMemoryDefinition`, which has a separate copy in each instance