Unless using the -a or -r options, do not parse floating point numbers in order to compare its numeric difference. Despite its name, fpcmp used used to compare every program output with its reference output even for programs that do not handle floating point and caused 0. and 0 to be always considered equal.
I the old behaviour is needed (as for the TSVC benchmark), floating point comparison with zero numeric tolerance can be enabled by explicitly setting -a 0 or -r 0.
Motivated by D128262.
I wonder if we shouldn't rather change the reference output. But fine with me if things aren't that easy to fix.