<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fixed point math in pure CPP</title>
	<atom:link href="http://manuel.bit-fire.com/2007/10/31/fixed-point-math-in-pure-cpp/feed/" rel="self" type="application/rss+xml" />
	<link>http://manuel.bit-fire.com/2007/10/31/fixed-point-math-in-pure-cpp/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Mar 2010 20:31:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Manuel</title>
		<link>http://manuel.bit-fire.com/2007/10/31/fixed-point-math-in-pure-cpp/comment-page-1/#comment-9655</link>
		<dc:creator>Manuel</dc:creator>
		<pubDate>Wed, 05 Dec 2007 23:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://manuel.bit-fire.com/?p=78#comment-9655</guid>
		<description>Thank you for your feedback Kurt: i performed various test at the time on a desktop machine, obviously with a release build, but on a Pentium D i didn’t notice improvements at all, floating point was showily faster than anything else.
It may be possible that my tests weren’t exhaustive as they should, i used a matrix-based test and a 3d rasterizer: both tests showed up big fixed point improvements on mobile platforms but none on the desktop.
I’ll try to search my old tests, too bad i don’t think i still have what i used at the time..
Have you played with compiling/linking options and stuff like that?</description>
		<content:encoded><![CDATA[<p>Thank you for your feedback Kurt: i performed various test at the time on a desktop machine, obviously with a release build, but on a Pentium D i didn’t notice improvements at all, floating point was showily faster than anything else.<br />
It may be possible that my tests weren’t exhaustive as they should, i used a matrix-based test and a 3d rasterizer: both tests showed up big fixed point improvements on mobile platforms but none on the desktop.<br />
I’ll try to search my old tests, too bad i don’t think i still have what i used at the time..<br />
Have you played with compiling/linking options and stuff like that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt Guntheroth</title>
		<link>http://manuel.bit-fire.com/2007/10/31/fixed-point-math-in-pure-cpp/comment-page-1/#comment-9654</link>
		<dc:creator>Kurt Guntheroth</dc:creator>
		<pubDate>Mon, 03 Dec 2007 21:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://manuel.bit-fire.com/?p=78#comment-9654</guid>
		<description>I am the “Kurt” referenced in the article. My experience is that fixed-point costs about 15% more than integer math, and is about twice as fast as floating point math on Intel Pentium-4 processors, and using Microsoft visual c++ versions from 6 to .Net-2005.

In evaluating the performance of fixed point arithmetic routines, it is important to compile a “release” build. On debug builds, the compiler creates function calls for all your template functions. Function call overhead eats the performance gains from using fixed point.</description>
		<content:encoded><![CDATA[<p>I am the “Kurt” referenced in the article. My experience is that fixed-point costs about 15% more than integer math, and is about twice as fast as floating point math on Intel Pentium-4 processors, and using Microsoft visual c++ versions from 6 to .Net-2005.</p>
<p>In evaluating the performance of fixed point arithmetic routines, it is important to compile a “release” build. On debug builds, the compiler creates function calls for all your template functions. Function call overhead eats the performance gains from using fixed point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
