<?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: Beware the InterlockedOr()</title>
	<atom:link href="http://kernelmustard.com/2006/07/25/beware-the-interlockedor/feed/" rel="self" type="application/rss+xml" />
	<link>http://kernelmustard.com/2006/07/25/beware-the-interlockedor/</link>
	<description>Reflections on software, security, and more by Steve Dispensa</description>
	<lastBuildDate>Sat, 13 Mar 2010 06:30:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kernel Mustard &#187; Blog Archive &#187; A definitive answer to the Interlocked code generation questions</title>
		<link>http://kernelmustard.com/2006/07/25/beware-the-interlockedor/comment-page-1/#comment-378</link>
		<dc:creator>Kernel Mustard &#187; Blog Archive &#187; A definitive answer to the Interlocked code generation questions</dc:creator>
		<pubDate>Wed, 02 Aug 2006 07:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://kernelmustard.com/2006/07/25/beware-the-interlockedor/#comment-378</guid>
		<description>[...] Mark Lacey, a developer who works on the compilers and related tools, has a great blog post up with a definitive explanation of the Interlocked* code generation issue that I mentioned before. He left a comment linking to his post, but I thought I&#8217;d link it from the main page since I did complain about this issue on the main page. [...]</description>
		<content:encoded><![CDATA[<p>[...] Mark Lacey, a developer who works on the compilers and related tools, has a great blog post up with a definitive explanation of the Interlocked* code generation issue that I mentioned before. He left a comment linking to his post, but I thought I&#8217;d link it from the main page since I did complain about this issue on the main page. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kernel Mustard &#187; Blog Archive &#187; More on the DDK interlocked bugs</title>
		<link>http://kernelmustard.com/2006/07/25/beware-the-interlockedor/comment-page-1/#comment-377</link>
		<dc:creator>Kernel Mustard &#187; Blog Archive &#187; More on the DDK interlocked bugs</dc:creator>
		<pubDate>Sat, 29 Jul 2006 05:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://kernelmustard.com/2006/07/25/beware-the-interlockedor/#comment-377</guid>
		<description>[...] According to some folks on USENET, it&#8217;s not just InterlockedOr() that&#8217;s broken (see my earlier post for background). [...]</description>
		<content:encoded><![CDATA[<p>[...] According to some folks on USENET, it&#8217;s not just InterlockedOr() that&#8217;s broken (see my earlier post for background). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
