Nick Fitzgerald

Results 226 issues of Nick Fitzgerald

Right now we generate bottom up, based on what is on the stack. This means that we pre-filter instructions that require "rare" stacks, making their generation even rarer. We should...

wasm-smith

The proposal advanced to phase 2 in today's CG meeting. @tlively PTAL, thanks!

nothing on the agenda, cancelling

The `rust-analyzer.cargo.targetDir` setting allows controlling the directory that `rust-analyzer` will use for build artifacts. It is useful to set this to something other than the default project's target directory because...

We should rewrite the core of the interpreter and its main loop such that we can easily flip a cargo feature on to start using nightly Rust's `feature(explicit_tail_calls)`. The way...

pulley

We should reimplement the DWARFwasm to DWARFnative transformation pass that implements the GDB/LLDB debugging support in Wasmtime by separating DWARF translation from DWARF traversal. We could do this by defining...

wasmtime:debugging

The null collector does not actually collect any garbage, it simply bump-allocates until the heap is exhausted, at which point further allocation attempts will fail. It does not require any...

wasmtime:api
fuzzing
wasmtime:ref-types
wasmtime:config

Right now we use the classic simple-fast algorithm (*A Simple, Fast Dominance Algorithm* by Cooper et al) and while this works well most of the time in practice, it has...

https://github.com/WebAssembly/memory-control

https://github.com/WebAssembly/shared-everything-threads