afl-compiler-fuzzer VS wasp

I use fuzzers, as every programmer should, and do not commit unless my compiler can be fuzzed for at least 24 hours without any crashes (if I were selling the software, I'd increase that period). I use AFL++ in LTO mode and comby-decomposer with a crappy script I made to collect crash test cases. I am also interested in afl-compiler-fuzzer, but have not yet tried it. Later, I'd like to try my hand at making a test generator that reaches codegen more often (no compile errors in the random source code). I use afl-tmin to minimize test cases, but the result is always illegible without manual work, and usually has extra junk the minimizer is incapable of deleting. Something like C-Reduce would be useful here.

I am currently experimenting with my own language wasp/angle:

https://github.com/pannous/wasp/wiki/

As you pointed out true GC is currently postponed, so no long running processes yet. The hope is to get the language finalized just in time when all wasm 2 features become standardized