News for hackers. Stuff that matters.
Re:The state of SIMD in Rust in 2025 by dbdr on Thursday November 06, 2025 @02:49AM (#45832592)
Is there a case involving NaN where they are not commutative? Do you mean getting a different bit-level representation of NaN?
Re:The state of SIMD in Rust in 2025 by Remnant44 on Thursday November 06, 2025 @04:04AM (#45833049)
In practical use for simd, various min/max operations. On Intel at least, they propagate nan or not based on operand order
Re:The state of SIMD in Rust in 2025 by boulos on Thursday November 06, 2025 @10:41AM (#45836420)
Also all comparisons.
Re:The state of SIMD in Rust in 2025 by jcranmer on Thursday November 06, 2025 @10:06AM (#45836082)
IEEE 754 doesn't (usually) distinguish between different NaN encodings for the purposes of semantics--if the result is a NaN, it doesn't specify which NaN the result is. Most hardware vendors implement a form of NaN propagation: when both inputs are NaN, one of the operands is returned, for example, always the left NaN is returned if both are NaN.

As a side note: all compilers I'm aware of make almost no guarantees on preserving the value of NaN payloads, hence they consider floating-point operations to be fully commutative, and there's no general way to guarantee that they evaluate in exactly the order you specified.