<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/1896013</link>
		<description>Comments by zeuxcg</description>
<item>
<title>Preshing on Programming : You Can Do Any Kind of Atomic Read-Modify-Write Operation</title>
<link>http://127.0.0.1:4000/20150402/you-can-do-any-kind-of-atomic-read-modify-write-operation#IDComment961464848</link>
<description>This is interesting. Is there any reason why std::atomic&amp;lt;T&amp;gt; can&amp;#039;t fail to compile if lock-free code can&amp;#039;t be generated? Silently making atomic operations non-atomic seems... bad. Or will atomic&amp;lt;T&amp;gt; with unsupported T compile to a code that uses a global mutex or something of the sort? </description>
<pubDate>Thu, 2 Apr 2015 15:39:30 +0000</pubDate>
<guid>http://127.0.0.1:4000/20150402/you-can-do-any-kind-of-atomic-read-modify-write-operation#IDComment961464848</guid>
</item>	</channel>
</rss>