<?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"
	>
<channel>
	<title>Comments on: # emerge osx-epic-fail</title>
	<atom:link href="http://www.vxrs.com/macintosh/emerge-osx-epic-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vxrs.com/macintosh/emerge-osx-epic-fail/</link>
	<description>Ponderings of things that go "Ping!" by Jeff Pickell</description>
	<pubDate>Thu, 20 Nov 2008 20:18:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jeff</title>
		<link>http://www.vxrs.com/macintosh/emerge-osx-epic-fail/#comment-3</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 03 Apr 2008 19:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.vxrs.com/?p=29#comment-3</guid>
		<description>Actually it was the subject of being able to specifically compile to the G4's altivec options that made me curious about using emerge.  On my intel-based macs I'll easily just stick w/fink or macports!</description>
		<content:encoded><![CDATA[<p>Actually it was the subject of being able to specifically compile to the G4&#8217;s altivec options that made me curious about using emerge.  On my intel-based macs I&#8217;ll easily just stick w/fink or macports!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Sebold</title>
		<link>http://www.vxrs.com/macintosh/emerge-osx-epic-fail/#comment-2</link>
		<dc:creator>Charles Sebold</dc:creator>
		<pubDate>Thu, 03 Apr 2008 19:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.vxrs.com/?p=29#comment-2</guid>
		<description>Debian apt can compile packages, but generally just gets the binary from the repository.

Testing has shown that, with the current state of optimization that the Intel processors are doing, it doesn't make sense to compile for your specific post-586 flavor; some tests showed that it was faster to use a generic i686 binary than it was to compile a tuned one for your processor.  (But of course I have no idea if that's true on G4 or G5s - probably not.)</description>
		<content:encoded><![CDATA[<p>Debian apt can compile packages, but generally just gets the binary from the repository.</p>
<p>Testing has shown that, with the current state of optimization that the Intel processors are doing, it doesn&#8217;t make sense to compile for your specific post-586 flavor; some tests showed that it was faster to use a generic i686 binary than it was to compile a tuned one for your processor.  (But of course I have no idea if that&#8217;s true on G4 or G5s - probably not.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
