<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Multithreading: hardware atomicity</title><link>http://msmvps.com/blogs/luisabreu/archive/2009/06/29/multithreading-hardware-atomicity.aspx</link><description>In the previous post , we’ve started looking at memory loads and stores reordering. In this post, we’re going to keep our study and we’re going to introduce atomicity. Atomicity is a really important concept we’ve met in the past. We’ve already talked</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Multithreading: using VolatileXXX instead of the volatile keyword</title><link>http://msmvps.com/blogs/luisabreu/archive/2009/06/29/multithreading-hardware-atomicity.aspx#1698559</link><pubDate>Tue, 07 Jul 2009 07:51:26 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1698559</guid><dc:creator>LA.NET [EN]</dc:creator><description>&lt;p&gt;[Update: Brad detected a flaw in the code: I had forgotten to initialize the _initialized field. Thanks&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1698559" width="1" height="1"&gt;</description></item></channel></rss>