<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: GCC Exception Frames</title>
	<link>http://www.airs.com/blog/archives/166</link>
	<description>Ian Lance Taylor</description>
	<pubDate>Wed,  8 Oct 2008 05:33:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on GCC Exception Frames by: Ian Lance Taylor</title>
		<link>http://www.airs.com/blog/archives/166#comment-11766</link>
		<pubDate>Thu, 27 Mar 2008 01:28:41 +0000</pubDate>
		<guid>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>Comment on GCC Exception Frames by: ncm</title>
		<link>http://www.airs.com/blog/archives/166#comment-11758</link>
		<pubDate>Wed, 26 Mar 2008 19:04:55 +0000</pubDate>
		<guid>http://www.airs.com/blog/archives/166#comment-11758</guid>
					<description>Sorry,  where is dl_iterate_phdr defined, and why couldn'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'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>
