Post

Nondeterminism in Futhark

A Futhark maintainer examines where a supposedly deterministic data-parallel language can produce different results: floating-point reduction order can vary across machines or runs, while conflicting scatter writes violate an unchecked precondition and can even produce torn values.

The useful distinction is between exact reproducibility, replaying the same schedule, and genuinely variable results. The post also explains why dynamically checking scatter conflicts with the operation’s performance cost model.