<?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: C Compilers</title>
	<atom:link href="http://blog.reverberate.org/2009/03/03/c-compilers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.reverberate.org/2009/03/03/c-compilers/</link>
	<description>parsing, performance, minimalism with C99</description>
	<lastBuildDate>Thu, 26 Jan 2012 04:15:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Phil</title>
		<link>http://blog.reverberate.org/2009/03/03/c-compilers/comment-page-1/#comment-1304</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Fri, 01 May 2009 03:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.reverberate.org/?p=146#comment-1304</guid>
		<description>Hey! It&#039;s been months! What happened?</description>
		<content:encoded><![CDATA[<p>Hey! It&#8217;s been months! What happened?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.reverberate.org/2009/03/03/c-compilers/comment-page-1/#comment-1302</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 20 Apr 2009 16:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.reverberate.org/?p=146#comment-1302</guid>
		<description>not to just chime in about another compiler a month later, but whatever.

There&#039;s also Watcom, which used to be a decent compiler especially due to the dos/4gw extender. I think it&#039;s been opensourced as OpenWatcom for a while, but it&#039;s development might be dead.</description>
		<content:encoded><![CDATA[<p>not to just chime in about another compiler a month later, but whatever.</p>
<p>There&#8217;s also Watcom, which used to be a decent compiler especially due to the dos/4gw extender. I think it&#8217;s been opensourced as OpenWatcom for a while, but it&#8217;s development might be dead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.reverberate.org/2009/03/03/c-compilers/comment-page-1/#comment-1280</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 03 Mar 2009 22:18:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.reverberate.org/?p=146#comment-1280</guid>
		<description>Don&apos;t forget the &lt;a href=&quot;http://www-01.ibm.com/software/awdtools/xlcpp/&quot; rel=&quot;nofollow&quot;&gt;IBM XL C compiler&lt;/a&gt; too

It&apos;s based on a GCC frontend, IIRC, so porting should be easy.  But it&apos;s worth adding to your list if you are truly looking for a complete set.

I&apos;ve so far managed to avoid using the PGI compilers personally, but I&apos;ve heard that they are (were?) sufficiently quirky to provide a decent test of your portability.

If you were really paranoid you could aim for C89-compliance with a few very common C99 features (this is what we do in MPICH2).  This mostly shouldn&apos;t matter though unless you want to run on machines that are just old or very exotic at this point.  Older Sun compilers in particular can be a nightmare.

Also, even if you do manage to make your software truly C89 or C99 compliant, there&apos;s still a good chance that you will have to work around some compiler quirks somewhere using autoconf or something similar in your build system (unless your project is sufficiently simple and high-level).  Just something to keep in mind.

-Dave</description>
		<content:encoded><![CDATA[<p>Don&apos;t forget the <a href="http://www-01.ibm.com/software/awdtools/xlcpp/" rel="nofollow">IBM XL C compiler</a> too</p>
<p>It&apos;s based on a GCC frontend, IIRC, so porting should be easy.  But it&apos;s worth adding to your list if you are truly looking for a complete set.</p>
<p>I&apos;ve so far managed to avoid using the PGI compilers personally, but I&apos;ve heard that they are (were?) sufficiently quirky to provide a decent test of your portability.</p>
<p>If you were really paranoid you could aim for C89-compliance with a few very common C99 features (this is what we do in MPICH2).  This mostly shouldn&apos;t matter though unless you want to run on machines that are just old or very exotic at this point.  Older Sun compilers in particular can be a nightmare.</p>
<p>Also, even if you do manage to make your software truly C89 or C99 compliant, there&apos;s still a good chance that you will have to work around some compiler quirks somewhere using autoconf or something similar in your build system (unless your project is sufficiently simple and high-level).  Just something to keep in mind.</p>
<p>-Dave</p>
]]></content:encoded>
	</item>
</channel>
</rss>

