Wouldn't the compiler optimize (x-y)!=0 to x!=y? Seems like a good optimisation to me and one probably in accordance to the C standard.

It would also make it impossible to have a decent non-zero check for

if ((x-y)!=0) progress((x-t)/(x-y));