<?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: Portland Group Adds Support for CUDA in PGI 2011 Development Tools</title>
	<atom:link href="http://insidehpc.com/2011/02/23/portland-group-adds-support-for-cuda-in-pgi-2011-development-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2011/02/23/portland-group-adds-support-for-cuda-in-pgi-2011-development-tools/</link>
	<description>HPC News Without the Noise for Supercomputing Professionals &#124; insideHPC</description>
	<lastBuildDate>Fri, 03 May 2013 04:44:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Tweets that mention Portland Group Adds Support for CUDA in PGI 2011 Development Tools &#124; insideHPC.com -- Topsy.com</title>
		<link>http://insidehpc.com/2011/02/23/portland-group-adds-support-for-cuda-in-pgi-2011-development-tools/#comment-307793</link>
		<dc:creator>Tweets that mention Portland Group Adds Support for CUDA in PGI 2011 Development Tools &#124; insideHPC.com -- Topsy.com</dc:creator>
		<pubDate>Wed, 23 Feb 2011 11:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=17650#comment-307793</guid>
		<description>[...] This post was mentioned on Twitter by insideHPC and Larry, Antonino Tumeo. Antonino Tumeo said: RT @insideHPC: Just in: Portland Group Adds Support for CUDA in PGI 2011 Development Tools http://bit.ly/h0OEIc [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by insideHPC and Larry, Antonino Tumeo. Antonino Tumeo said: RT @insideHPC: Just in: Portland Group Adds Support for CUDA in PGI 2011 Development Tools <a href="http://bit.ly/h0OEIc" rel="nofollow">http://bit.ly/h0OEIc</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
