Comments on: Floating point is slow, you say? http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/ The road to 42. Sun, 13 Dec 2009 02:16:04 +0000 http://wordpress.com/ hourly 1 By: Wrong http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-106 Wrong Wed, 26 Nov 2008 15:31:16 +0000 http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-106 This is generating overflow in no time! Hence, the only thing that has to be done for the floating point version after a few iterations is to add 1 to NaN (==NaN), which the CPU should be able to find out very fast. The integer version is having the same problem, but the resulting value is still a valid integer. This is generating overflow in no time! Hence, the only thing that has to be done for the floating point version after a few iterations is to add 1 to NaN (==NaN), which the CPU should be able to find out very fast. The integer version is having the same problem, but the resulting value is still a valid integer.

]]> By: antipattern http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-39 antipattern Fri, 19 Oct 2007 14:06:25 +0000 http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-39 Well yes, that was my first reaction too. But in all three cases the iteration is still there in the generated assembly listing. The instructions generated are native. CLR requires the "/clr" switch. Even in CLR the iteration is there. Well yes, that was my first reaction too. But in all three cases the iteration is still there in the generated assembly listing.

The instructions generated are native. CLR requires the “/clr” switch. Even in CLR the iteration is there.

]]> By: Lars Gregersen http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-38 Lars Gregersen Thu, 18 Oct 2007 21:52:26 +0000 http://antipattern.wordpress.com/2007/10/17/floating-point-is-slow-you-say/#comment-38 I would check what instructions (native or CLR) are created. A clever optimizer would see that the result isn't really needed and simply skip the entire loop. I would check what instructions (native or CLR) are created.

A clever optimizer would see that the result isn’t really needed and simply skip the entire loop.

]]>