<?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 for Tom Distler</title>
	<atom:link href="http://tdistler.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://tdistler.com</link>
	<description></description>
	<pubDate>Thu, 11 Mar 2010 04:02:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on C/C++: Using Bitfields Effectively by micahc</title>
		<link>http://tdistler.com/2008/07/21/cc-using-bitfields-effectively/comment-page-1#comment-5183</link>
		<dc:creator>micahc</dc:creator>
		<pubDate>Sun, 24 Jan 2010 20:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=120#comment-5183</guid>
		<description>I would say that you should still lock the entire operation, from the caching to the writing back from the cache. If you don't, what happens when you read, release the lock, and then get interrupted by a process that manages to acquire the lock, cache, release the lock, perform the same block processing you were going to do, but with an updated register, reaquire the lock again, and then write. When the first thread runs again it will the clobber the register.</description>
		<content:encoded><![CDATA[<p>I would say that you should still lock the entire operation, from the caching to the writing back from the cache. If you don&#8217;t, what happens when you read, release the lock, and then get interrupted by a process that manages to acquire the lock, cache, release the lock, perform the same block processing you were going to do, but with an updated register, reaquire the lock again, and then write. When the first thread runs again it will the clobber the register.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 4th of July, 2008 by Tom</title>
		<link>http://tdistler.com/2008/07/04/4th-of-july-2008/comment-page-1#comment-4996</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 12 Jan 2010 17:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=108#comment-4996</guid>
		<description>No argument here.</description>
		<content:encoded><![CDATA[<p>No argument here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 4th of July, 2008 by Backlash</title>
		<link>http://tdistler.com/2008/07/04/4th-of-july-2008/comment-page-1#comment-4989</link>
		<dc:creator>Backlash</dc:creator>
		<pubDate>Tue, 12 Jan 2010 11:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=108#comment-4989</guid>
		<description>US: historically ignorant since 1776 AC</description>
		<content:encoded><![CDATA[<p>US: historically ignorant since 1776 AC</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Screwdriver Warning Label by Frank</title>
		<link>http://tdistler.com/2007/08/16/screwdriver-warning-label/comment-page-1#comment-4809</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Thu, 17 Dec 2009 08:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=51#comment-4809</guid>
		<description>Wow! this is stupid!</description>
		<content:encoded><![CDATA[<p>Wow! this is stupid!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Screwdriver Warning Label by John</title>
		<link>http://tdistler.com/2007/08/16/screwdriver-warning-label/comment-page-1#comment-4808</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 17 Dec 2009 08:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=51#comment-4808</guid>
		<description>The person who was the cause of this warning to be placed on this product should be dragged in public and made to reveal the reason why they thought this was a good idea!</description>
		<content:encoded><![CDATA[<p>The person who was the cause of this warning to be placed on this product should be dragged in public and made to reveal the reason why they thought this was a good idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Print a Stack Backtrace Programatically in Linux by Web Development London</title>
		<link>http://tdistler.com/2008/11/15/how-to-print-a-stack-backtrace-programatically-in-linux/comment-page-1#comment-4752</link>
		<dc:creator>Web Development London</dc:creator>
		<pubDate>Wed, 02 Dec 2009 12:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=149#comment-4752</guid>
		<description>Hey, that was interesting,

Some great linux advice,

Anyway, thanks for the post</description>
		<content:encoded><![CDATA[<p>Hey, that was interesting,</p>
<p>Some great linux advice,</p>
<p>Anyway, thanks for the post</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Motivational Poster: Motivation by bagelboy</title>
		<link>http://tdistler.com/2008/06/28/motivational-poster-motivation/comment-page-1#comment-4740</link>
		<dc:creator>bagelboy</dc:creator>
		<pubDate>Mon, 30 Nov 2009 21:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=104#comment-4740</guid>
		<description>Never before nor since has a movie been made so honestly.  This is seriously how I feel most of the time.  And the other times, I'm lazy.</description>
		<content:encoded><![CDATA[<p>Never before nor since has a movie been made so honestly.  This is seriously how I feel most of the time.  And the other times, I&#8217;m lazy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sed Regular Expression: Find Lines Not Matching A String by bespoke software</title>
		<link>http://tdistler.com/2009/04/17/sed-regular-expression-find-lines-not-matching-a-string/comment-page-1#comment-4635</link>
		<dc:creator>bespoke software</dc:creator>
		<pubDate>Thu, 05 Nov 2009 09:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=218#comment-4635</guid>
		<description>Humm... interesting,

This is really helpful,

Stream editor has never been so easy,

Anyway, thanks for the post,

Keep up the good work,</description>
		<content:encoded><![CDATA[<p>Humm&#8230; interesting,</p>
<p>This is really helpful,</p>
<p>Stream editor has never been so easy,</p>
<p>Anyway, thanks for the post,</p>
<p>Keep up the good work,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ASCII Video Rendering by software development london</title>
		<link>http://tdistler.com/2008/10/03/ascii-video-rendering/comment-page-1#comment-4550</link>
		<dc:creator>software development london</dc:creator>
		<pubDate>Fri, 16 Oct 2009 15:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=140#comment-4550</guid>
		<description>Thta was an inspiring post,

thanks for providing the info on libcaca but can you watch the video in full screen

Thanks for writing, most people don't bother.</description>
		<content:encoded><![CDATA[<p>Thta was an inspiring post,</p>
<p>thanks for providing the info on libcaca but can you watch the video in full screen</p>
<p>Thanks for writing, most people don&#8217;t bother.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging: C++ Templates, Breakpoints, and GDB by Anon</title>
		<link>http://tdistler.com/2008/11/13/debugging-c-templates-brekpoints-and-gdb/comment-page-1#comment-4517</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Wed, 07 Oct 2009 21:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://tdistler.com/?p=146#comment-4517</guid>
		<description>Looks like you've a spelling mistake in your title

s/brekpoints/breakpoints

   Cheers</description>
		<content:encoded><![CDATA[<p>Looks like you&#8217;ve a spelling mistake in your title</p>
<p>s/brekpoints/breakpoints</p>
<p>   Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
