On Wednesday 25 May 2005 16:22, chris jefferson wrote: > > On the other hand, in general using != and == on floating point numbers > is always dangerous if you do not know all the consequences. For > example, on your above program if I use 30.1 and 90.3, the program fails > without -ffast-math. > Yes. I still don't understand why gcc doesn't do -ffast-math by default like all other compilers. The people who needs perfect standard behavior are a lot fewer than all the packagers who doesn't understand which optimization flags gcc should _always_ be called with.
`Allan
