Andrew Scheidecker
Andrew Scheidecker
Imagine that a `memory.shrink` operation is added, and that a thread waits on an address, then the memory is shrunk so that the address is out of bounds. If wake...
AFAICT for the current web embedding of WebAssembly, globals are effectively thread-local: you have to create a new instance of a module for each JavaScript worker, so any mutable globals...
https://github.com/WebAssembly/simd/issues/118 was started in response to [another issue](https://github.com/emscripten-core/emscripten/issues/9340) concerning performance of loading deinterleaved data. The code in question is a port of [some OpenCV SSE code](https://github.com/opencv/opencv/blob/cc9b199ecbca3e917b9c53c3aa20664504e52c00/modules/core/include/opencv2/core/hal/intrin_sse.hpp#L2011) to WASM SIMD: they...
My primary concern with WebAssembly right now is not anything in the current spec, but rather that the design anticipates the addition of GC reference types. I think this is...
Seeing the [shared memory atomics proposal](https://github.com/WebAssembly/design/pull/1019) and the [SIMD proposal](https://github.com/WebAssembly/design/issues/1035), it struck me that it will be painful if they are not orthogonal to the [planned feature](https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#multiple-tables-and-memories) to allow accesses...
The current design has a hidden table of implementation-defined objects that are indexed by the integer "file descriptors" exposed through the API. These "file descriptors" could be more generally called...
As requested [here](https://github.com/WebAssembly/wasm-c-api/issues/80#issuecomment-548530127), this adds a .clang-format that only contains `BasedOnStyle: Chromium`, and applies it to *.c, *.cc, *.h, and *.hh, so folks can see what the impact is.
This would make it much easier for collaborators to ensure their changes have formatting that is consistent with the rest of the repo. I'm locally using a `.clang-format` that just...
The API for getting a table element doesn't directly expose the possibility for the access to fail due to bounds checking: ```c own wasm_ref_t* wasm_table_get(const wasm_table_t*, wasm_table_size_t index); ``` Perhaps...
The API currently exposes the contents of a memory as: ```c byte_t* wasm_memory_data(wasm_memory_t*); size_t wasm_memory_data_size(const wasm_memory_t*); ``` This effectively delegates the bounds checking to the API client. The problem is...