crypto/md5 — validation proof
Go’s own crypto/md5 test suite, converted to C# by go2cs, built against the converted standard
library, run under the Go-semantics test host, and compared verdict for verdict against a clean
go test -json baseline of the same sources. This page is generated by the converter from that
comparison — it is the evidence behind the crypto/md5 row in
Validated Test Packages.
Validated 2026-10-25 · converter 3e3f18925
14 matched · 1 disclosed — Go 1.26.10, windows/amd64, converted package
src/core/crypto/md5.
Measured at Release (tiered JIT off), oracle go version go1.26.10 windows/amd64.
Verdicts
| Test | go test |
go2cs |
|---|---|---|
TestAllocations |
pass | fail (disclosed) |
TestBlockGeneric |
pass | pass |
TestExtraLarge |
pass | pass |
TestExtraMethods |
pass | pass |
TestGolden |
pass | pass |
TestGoldenMarshal |
pass | pass |
TestLarge |
pass | pass |
TestLargeHashes |
pass | pass |
TestMD5Hash |
pass | pass |
TestMD5Hash/Clone |
pass | pass |
TestMD5Hash/OutOfBoundsRead |
pass | pass |
TestMD5Hash/ResetState |
pass | pass |
TestMD5Hash/StatefulWrite |
pass | pass |
TestMD5Hash/SumAppend |
pass | pass |
TestMD5Hash/WriteWithoutError |
pass | pass |
Disclosed divergences
A disclosed divergence is a specific Go assertion this conversion does not satisfy — not
a skipped test and not a tolerance. Each one is pinned by exact failure signature in the package’s
hand-owned go2cs_test_disclosures.json;
a disclosed test that fails any other way is still a hard mismatch.
The Class column says which kind each one is: a deferred entry is an assertion the managed
CLR can meet, pinned against the named plan that will retire it; every other class is one it
provably cannot satisfy.
| Test | Class | Pinned reason |
|---|---|---|
TestAllocations |
deferred |
want-zero AllocsPerRun assert: Sum copies the digest (d0 := *d) so the caller can keep writing, and that copy must deep-copy the digest’s [4]uint32 state and [64]byte block — golib’s array |
Excluded declarations
Declarations filtered from both sides of the comparison, and therefore not claimed above:
Benchmark, Fuzz and Example declarations the converted host does not execute, plus any
test requiring a capability the managed runtime does not provide — a testing member the host
has not implemented, or a platform behavior it provably cannot reproduce. Each is named with
the capability it needs.
- BenchmarkHash128 (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash1K (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash1KUnaligned (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash1M (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash256 (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash512 (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash64 (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash8Bytes (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash8BytesUnaligned (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash8K (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash8KUnaligned (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkHash8M (benchmark): benchmark execution is deferred to Phase 4D
- ExampleNew (example): example execution is deferred to Phase 4D
- ExampleNew_file (example): example execution is deferred to Phase 4D
- ExampleSum (example): example execution is deferred to Phase 4D