Wouter van Oortmerssen
Wouter van Oortmerssen
I see IT as crucial puzzle piece for the Wasm eco system, and I keep seeing new proposals and ideas that could benefit from it being available. Yet at the...
The "median" target for this proposal appears to be Java-like languages (though others can certainly be represented) which will heavily make use of vtable calls. In that light, it seems...
I generally feel the proposal is very elegant (in particular, being based on low level structs that are not assigned a particular semantics) and appears to be well positioned to...
This is not an "issue" for the current proposal, more of a remark, but curious if people see any use for it. With the current proposal, the way a multi-threaded...
**ezQuake version:** 3.6-dev-alpha8 **OS/device including version:** Nvidia 3080 drivers 471.11, using glsl path **Describe the bug** Will crash with `offset < glBuffersState.buffers[id].size` assertion failure (`gl_buffers.c`, line 380) upon map end...
`wasm-decompile` works almost identically to `wasm2wat` (and is also part of WABT) so presumably could be an alternative option in this plugin. Details: https://github.com/WebAssembly/wabt/blob/master/docs/decompiler.md @RReverser
There are a number of operations in Wasm that are `i32` only, mainly because they are deemed booleans, primarily among them `if`, `br_if` and `select`. Because pointers were 32-bit, and...
With a 64-bit address space, we don't just get to break the 4GB barrier, but potentially new programming techniques become available, in particular techniques that rely on using larger parts...
In `static size_t _memory_span_list_push(span_t** head, span_t* span)`, `span` is clearly pointing to memory with garbage values. This is with `#define TRACY_ON_DEMAND 1` with never any profiler connected so ideally tracy...
Followed your instructions exactly (did not have Rust nor VulkanSDK installed, so they are all the latests stable versions), and `cargo run --release --bin rendersdf` gives me: ``` error[E0432]: unresolved...