<?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: Compiler Quality and C&#8217;s volatile Keyword</title>
	<atom:link href="http://embeddedgurus.com/barr-code/2007/12/compiler-quality-and-cs-volatile-keyword/feed/" rel="self" type="application/rss+xml" />
	<link>http://embeddedgurus.com/barr-code/2007/12/compiler-quality-and-cs-volatile-keyword/</link>
	<description>A Blog by Michael Barr</description>
	<lastBuildDate>Thu, 17 Jun 2010 17:17:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://embeddedgurus.com/barr-code/2007/12/compiler-quality-and-cs-volatile-keyword/comment-page-1/#comment-20</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 07 Jan 2010 19:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2007/12/06/compiler-quality-and-cs-volatile-keyword/#comment-20</guid>
		<description>Some years ago in developing a rather large diagnostics module, a colleague spent a great deal of time getting his code to work and was quite proud when all of his normal testing passed. Then, when the test organization tried various failure test cases, the module could not handle any case. Turns out, he failed to use &quot;volatile&quot; anywhere on the memory-based device registers, and the GCC C compiler optimized out entire procedures and large code sequences. A significant and frustrated rework was required. (Code review? What&#039;s that?)</description>
		<content:encoded><![CDATA[<p>Some years ago in developing a rather large diagnostics module, a colleague spent a great deal of time getting his code to work and was quite proud when all of his normal testing passed. Then, when the test organization tried various failure test cases, the module could not handle any case. Turns out, he failed to use &quot;volatile&quot; anywhere on the memory-based device registers, and the GCC C compiler optimized out entire procedures and large code sequences. A significant and frustrated rework was required. (Code review? What&#39;s that?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kalpak dabir</title>
		<link>http://embeddedgurus.com/barr-code/2007/12/compiler-quality-and-cs-volatile-keyword/comment-page-1/#comment-19</link>
		<dc:creator>kalpak dabir</dc:creator>
		<pubDate>Sun, 18 Oct 2009 05:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2007/12/06/compiler-quality-and-cs-volatile-keyword/#comment-19</guid>
		<description>Price is not a reliable benchmark. Found such a bug in a high end automotive grade compiler for NEC chip. Required diving into assembly to confirm bug and create work around in C.kalpak dabir</description>
		<content:encoded><![CDATA[<p>Price is not a reliable benchmark. Found such a bug in a high end automotive grade compiler for NEC chip. Required diving into assembly to confirm bug and create work around in C.kalpak dabir</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://embeddedgurus.com/barr-code/2007/12/compiler-quality-and-cs-volatile-keyword/comment-page-1/#comment-18</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 18 Apr 2008 16:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfcdev.org/test-stack/2007/12/06/compiler-quality-and-cs-volatile-keyword/#comment-18</guid>
		<description>Michael-The situation regarding compilation of volatile accesses is worse than you indicate here, and paying money for a compiler is no guarantee.  If you get a minute check out &lt;a HREF=&quot;http://www.cs.utah.edu/~regehr/papers/emsoft08_submit.pdf&quot; rel=&quot;nofollow&quot;&gt;some work that we recently wrote up&lt;/a&gt; on this subject.John Regehr</description>
		<content:encoded><![CDATA[<p>Michael-The situation regarding compilation of volatile accesses is worse than you indicate here, and paying money for a compiler is no guarantee.  If you get a minute check out <a HREF="http://www.cs.utah.edu/~regehr/papers/emsoft08_submit.pdf" rel="nofollow">some work that we recently wrote up</a> on this subject.John Regehr</p>
]]></content:encoded>
	</item>
</channel>
</rss>
