<?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: GCC Exception Frames</title>
	<atom:link href="http://www.airs.com/blog/archives/166/feed" rel="self" type="application/rss+xml" />
	<link>http://www.airs.com/blog/archives/166</link>
	<description>Ian Lance Taylor</description>
	<lastBuildDate>Mon, 15 Mar 2010 16:54:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ian Lance Taylor</title>
		<link>http://www.airs.com/blog/archives/166/comment-page-1#comment-11766</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Thu, 27 Mar 2008 01:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/166#comment-11766</guid>
		<description>dl_iterate_phdr is provided by the dynamic linker.  It is declared in .

I guess you are suggesting: why not put the unwind code in the dynamic linker?  In principle we could do that someday.  In practice that would fix the ABI and API not merely the ABI of the unwind information, which is already fixed, but also the ABI and API of the unwinder.  That might be desirable at some point, but for now I think it would be better to let the compiler continue own it.</description>
		<content:encoded><![CDATA[<p>dl_iterate_phdr is provided by the dynamic linker.  It is declared in .</p>
<p>I guess you are suggesting: why not put the unwind code in the dynamic linker?  In principle we could do that someday.  In practice that would fix the ABI and API not merely the ABI of the unwind information, which is already fixed, but also the ABI and API of the unwinder.  That might be desirable at some point, but for now I think it would be better to let the compiler continue own it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ncm</title>
		<link>http://www.airs.com/blog/archives/166/comment-page-1#comment-11758</link>
		<dc:creator>ncm</dc:creator>
		<pubDate>Wed, 26 Mar 2008 19:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/166#comment-11758</guid>
		<description>Sorry,  where is dl_iterate_phdr defined, and why couldn&#039;t the present contents of libgcc_s.so be there, too, similarly obviating libgcc_s.so without need to build with --eh-frame-hdr?  I think I&#039;m still missing some context.</description>
		<content:encoded><![CDATA[<p>Sorry,  where is dl_iterate_phdr defined, and why couldn&#8217;t the present contents of libgcc_s.so be there, too, similarly obviating libgcc_s.so without need to build with &#8211;eh-frame-hdr?  I think I&#8217;m still missing some context.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
