playX18

Initial work on Fuzzer randomization

1

Resolves #3988. # Notes At the moment this PR contains simple implementation, I am still working on making this randomization better. At the moment some runs show success rates of...

chore: debug assert reservation states in process_success

1

@breathx

Randomization of fuzzer configuration through `arbitrary` crate

1

### Problem to Solve At the moment fuzzer config and what we pass to `wasm-smith` for WASM generation is mostly static, this does not allow us to get fully randomized...

New PR based on #4288 but with cleaner code and solution that does not break a fuzzer. Still WIP but all that is left is write a migration and fix...

# Proposal On last call everyone agreed it is a good idea to get rid of syscalls like send_commit, send_push and others. Rationale for this is that these syscalls: -...

How was encodings made?

2

Is it hand-made or somehow parsed from Intel manual? I am using `instrs.txt` in my project but looking to add RW info for operands and doing it by hand is...

Support multiple-return values in singlepass compiler

1

### Motivation Rust enabled multiple returns values in WASM targets in stable which means if you're compiling now it might be possible that WASM is produced with multiple return values...

Add tracking functionality for memory management in allocators

1

Added `track.rs` which provides simple utility functions to track memory allocated by MMTk using `crabgrind` crate. When `crabgrind` feature is not enabled all functions are no-ops.

In the function here: https://github.com/mmtk/mmtk-core/blob/master/src/util/alloc/allocator.rs#L90 the assumption is that ALIGNMENT_VALUE fits into BYTES_IN_INT, but BYTES_IN_INT is `4` everywhere while `ALIGNMENT_VALUE` is defined as `usize`. On top of that it does...