From 6e8f5175e27676d8e2f663c2f15b7b5f6cffe0ab Mon Sep 17 00:00:00 2001 From: Andrew Noyes Date: Wed, 18 Nov 2026 14:18:31 -0500 Subject: [PATCH] Remove the recorded validation snapshot The table was a one-off measurement on a particular machine. Keep the commands and the properties they check; readers can run them for current numbers. --- cpp/README.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/cpp/README.md b/cpp/README.md index 8490f65..e02d8e9 100644 --- a/cpp/README.md +++ b/cpp/README.md @@ -167,17 +167,6 @@ requires exact endpoints. `fuzz_raw` only checks memory safety and undefined behaviour for arbitrary (possibly unreadable) inputs. -One representative validation run on this machine: - -| check | cases / runs | result | -| --- | ---: | --- | -| literal vs. Lean golden vectors | 40,000 | 0 mismatches (exact endpoints) | -| fast vs. literal on sorted corpus | 18,971 | 0 mismatches | -| extreme-offset regression (`extreme_test`) | 7,574 | 0 mismatches | -| finite readable sweep (`sweep_test`) | 13,565,772 | 0 mismatches | -| readable differential fuzzing (60 s) | 1,182,424 | 0 mismatches | -| raw safety fuzzing (60 s) | 1,905,270 | no ASan/UBSan findings | - `extreme_test` covers offsets the fuzzers deliberately avoid (they draw offsets from `[-256, 255]`). Both implementations decide the closed form's `keyAfterN n k < upper` test from the key lengths (`keyAfterNLt`) rather than