<?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: Efficient C Tips #4 &#8211; Use Speed Optimization</title>
	<atom:link href="http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/feed/" rel="self" type="application/rss+xml" />
	<link>http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/</link>
	<description>Thoughts on embedded systems by Nigel Jones</description>
	<lastBuildDate>Sun, 06 May 2012 10:34:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Eric Miller</title>
		<link>http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/comment-page-1/#comment-14409</link>
		<dc:creator>Eric Miller</dc:creator>
		<pubDate>Tue, 14 Feb 2012 20:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2008/09/08/efficient-c-tips-4-use-speed-optimization/#comment-14409</guid>
		<description>I&#039;ve gone in the opposite direction: using size optimization after getting burned by &quot;speed optimization.&quot;

One particular speed optimization in particular (loop unrolling) can cause code size to balloon, introducing i-cache misses into code that fits in cache when size optimized.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve gone in the opposite direction: using size optimization after getting burned by &#8220;speed optimization.&#8221;</p>
<p>One particular speed optimization in particular (loop unrolling) can cause code size to balloon, introducing i-cache misses into code that fits in cache when size optimized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/comment-page-1/#comment-55</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 23 Sep 2008 08:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2008/09/08/efficient-c-tips-4-use-speed-optimization/#comment-55</guid>
		<description>what are the different size optimization methods?</description>
		<content:encoded><![CDATA[<p>what are the different size optimization methods?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Jones</title>
		<link>http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/comment-page-1/#comment-54</link>
		<dc:creator>Nigel Jones</dc:creator>
		<pubDate>Mon, 15 Sep 2008 11:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2008/09/08/efficient-c-tips-4-use-speed-optimization/#comment-54</guid>
		<description>I think the point of the post was that most of the time in an embedded system you &lt;b&gt;can&lt;/b&gt; afford to use speed optimization. Unfortunately most compilers are set up to use size optimization and most of us are taught that small size code is good - without fully understanding what it can cost us.</description>
		<content:encoded><![CDATA[<p>I think the point of the post was that most of the time in an embedded system you <b>can</b> afford to use speed optimization. Unfortunately most compilers are set up to use size optimization and most of us are taught that small size code is good &#8211; without fully understanding what it can cost us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://embeddedgurus.com/stack-overflow/2008/09/efficient-c-tips-4-use-speed-optimization/comment-page-1/#comment-53</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 15 Sep 2008 11:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2008/09/08/efficient-c-tips-4-use-speed-optimization/#comment-53</guid>
		<description>There ofcourse are more speed optimizations that are killing code size. Loop unrolling, automatic function inlining are just two examples. In general: use size optimizations where you need to, use speed optimizations if you can affortd to...</description>
		<content:encoded><![CDATA[<p>There ofcourse are more speed optimizations that are killing code size. Loop unrolling, automatic function inlining are just two examples. In general: use size optimizations where you need to, use speed optimizations if you can affortd to&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

