> The point is that the primitives that you work with on GPUs are non-deterministic by design.
This is just blatantly wrong. There are _some_ operations that can be non-deterministic in some scenarios but they are not necessary.
GPUs are deterministic. If you ask them to add a million floats in order, you get the same result every time. If you ask them to add a million floats in some arbitrary order, then you may get different results every time. The distinction is that someone had to ask the GPU to do that. It's a choice.
> I mostly take issue with you phrasing it as a bug and using it to insult the authors.
It's a bug, whether it insults the authors or not is irrelevant. It's most definitely a bug.
> The point is that the primitives that you work with on GPUs are non-deterministic by design.
This is just blatantly wrong. There are _some_ operations that can be non-deterministic in some scenarios but they are not necessary.
GPUs are deterministic. If you ask them to add a million floats in order, you get the same result every time. If you ask them to add a million floats in some arbitrary order, then you may get different results every time. The distinction is that someone had to ask the GPU to do that. It's a choice.
> I mostly take issue with you phrasing it as a bug and using it to insult the authors.
It's a bug, whether it insults the authors or not is irrelevant. It's most definitely a bug.