<?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 Summit</title>
	<atom:link href="http://www.airs.com/blog/archives/209/feed" rel="self" type="application/rss+xml" />
	<link>http://www.airs.com/blog/archives/209</link>
	<description>Ian Lance Taylor</description>
	<lastBuildDate>Sun, 07 Mar 2010 17:12:02 +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/209/comment-page-1#comment-15056</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Thu, 06 Nov 2008 01:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-15056</guid>
		<description>I did create the branch, called gcc-in-cxx.  Tom Tromey and I have done some work on it.  A lot more of gcc builds in C++ now, but it still doesn&#039;t bootstrap.</description>
		<content:encoded><![CDATA[<p>I did create the branch, called gcc-in-cxx.  Tom Tromey and I have done some work on it.  A lot more of gcc builds in C++ now, but it still doesn&#8217;t bootstrap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sulfide</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-15051</link>
		<dc:creator>sulfide</dc:creator>
		<pubDate>Wed, 05 Nov 2008 15:20:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-15051</guid>
		<description>when are we going to see some c++ in gcc, did you ever create that branch gcc-to-c++?</description>
		<content:encoded><![CDATA[<p>when are we going to see some c++ in gcc, did you ever create that branch gcc-to-c++?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lance Taylor</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14392</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Sun, 06 Jul 2008 06:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14392</guid>
		<description>The VEC or vector slide isn&#039;t clear as it is--I hope it was more clear when I talked about it!  The C++ code isn&#039;t meant to be real code.  Instead, each line is the C++ version of the corresponding line in the C code.  Thus, &quot;VEC_reserve (loop_p, gc, superloops, depth);&quot; in C is the same as &quot;superloops-&gt;reserve(depth);&quot;.

You&#039;re quite right about &quot;superloops[depth]&quot;.  That should have been &quot;(*superloops)[depth]&quot; as you suggest.  Thanks.</description>
		<content:encoded><![CDATA[<p>The VEC or vector slide isn&#8217;t clear as it is&#8211;I hope it was more clear when I talked about it!  The C++ code isn&#8217;t meant to be real code.  Instead, each line is the C++ version of the corresponding line in the C code.  Thus, &#8220;VEC_reserve (loop_p, gc, superloops, depth);&#8221; in C is the same as &#8220;superloops-&gt;reserve(depth);&#8221;.</p>
<p>You&#8217;re quite right about &#8220;superloops[depth]&#8220;.  That should have been &#8220;(*superloops)[depth]&#8221; as you suggest.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt.godbolt</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14365</link>
		<dc:creator>matt.godbolt</dc:creator>
		<pubDate>Wed, 02 Jul 2008 10:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14365</guid>
		<description>Great blog, and great presentations there.  A quick nitpick, unless I&#039;ve missed something, in your slide in the C++ GCC &quot;VEC or vector&quot;, I think the C++ side has a couple of issues.  First up, the std::vector object isn&#039;t assigned or allocated (I realise this may just be for clarity!)  More importantly, the accessor &quot;superloops[depth]&quot; will almost certainly segfault for depth!=0.  I think it should be &quot;(*superloops)[depth]&quot;, or maybe &quot;superloops-&gt;at(depth)&quot;.

Of course, I may have missed something along the way there, but the pedant in me couldn&#039;t help posting here...

I&#039;m very excited about the future of the linker, and look forward to the planned cool new features.</description>
		<content:encoded><![CDATA[<p>Great blog, and great presentations there.  A quick nitpick, unless I&#8217;ve missed something, in your slide in the C++ GCC &#8220;VEC or vector&#8221;, I think the C++ side has a couple of issues.  First up, the std::vector object isn&#8217;t assigned or allocated (I realise this may just be for clarity!)  More importantly, the accessor &#8220;superloops[depth]&#8221; will almost certainly segfault for depth!=0.  I think it should be &#8220;(*superloops)[depth]&#8220;, or maybe &#8220;superloops-&gt;at(depth)&#8221;.</p>
<p>Of course, I may have missed something along the way there, but the pedant in me couldn&#8217;t help posting here&#8230;</p>
<p>I&#8217;m very excited about the future of the linker, and look forward to the planned cool new features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lance Taylor</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14289</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14289</guid>
		<description>By the way, you can find the source for the slides &lt;a href=&quot;http://airs.com/ian/pubs.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>By the way, you can find the source for the slides <a href="http://airs.com/ian/pubs.html" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lance Taylor</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14288</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14288</guid>
		<description>I&#039;m glad people liked the slides.  I do indeed use beamer, with the Goettingen theme.

EdgeWiseInAnnArbor: I&#039;m not sure that the autopackage site is really talking about the common case.  If you force deep binding, then symbol interposition no longer works as you expect.  In general ELF tries to make symbol interposition work, so that you can use LD_PRELOAD, etc.  If you can&#039;t live with that, then use dlopen with RTLD_DEEPBIND.  dlopen is of course also the way to implement their suggested DT_USEFUL.  ELF definitely makes complicated things complicated.  But the simple case does generally do what people expect, especially when you realize that symbol interposition is a goal.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad people liked the slides.  I do indeed use beamer, with the Goettingen theme.</p>
<p>EdgeWiseInAnnArbor: I&#8217;m not sure that the autopackage site is really talking about the common case.  If you force deep binding, then symbol interposition no longer works as you expect.  In general ELF tries to make symbol interposition work, so that you can use LD_PRELOAD, etc.  If you can&#8217;t live with that, then use dlopen with RTLD_DEEPBIND.  dlopen is of course also the way to implement their suggested DT_USEFUL.  ELF definitely makes complicated things complicated.  But the simple case does generally do what people expect, especially when you realize that symbol interposition is a goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davem</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14286</link>
		<dc:creator>davem</dc:creator>
		<pubDate>Wed, 18 Jun 2008 20:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14286</guid>
		<description>I think he used the &#039;beamer&#039; latex package.  That&#039;s my guess because his
slides look similar in style to mine and that&#039;s what I&#039;ve been using lately.

And indeed a &quot;strings gold-slides.pdf &#124; egrep -i LaTeX&quot; reveals:

LaTeX with beamer class version 3.01</description>
		<content:encoded><![CDATA[<p>I think he used the &#8216;beamer&#8217; latex package.  That&#8217;s my guess because his<br />
slides look similar in style to mine and that&#8217;s what I&#8217;ve been using lately.</p>
<p>And indeed a &#8220;strings gold-slides.pdf | egrep -i LaTeX&#8221; reveals:</p>
<p>LaTeX with beamer class version 3.01</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bgamari</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14285</link>
		<dc:creator>bgamari</dc:creator>
		<pubDate>Wed, 18 Jun 2008 19:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14285</guid>
		<description>The slides look to me like they were done in beamer, an extremely well-done latex extension.</description>
		<content:encoded><![CDATA[<p>The slides look to me like they were done in beamer, an extremely well-done latex extension.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: graydon</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14284</link>
		<dc:creator>graydon</dc:creator>
		<pubDate>Wed, 18 Jun 2008 17:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14284</guid>
		<description>Nice presentations. Unrelated question: what did you use for the slides?</description>
		<content:encoded><![CDATA[<p>Nice presentations. Unrelated question: what did you use for the slides?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EdgeWiseInAnnArbor</title>
		<link>http://www.airs.com/blog/archives/209/comment-page-1#comment-14282</link>
		<dc:creator>EdgeWiseInAnnArbor</dc:creator>
		<pubDate>Wed, 18 Jun 2008 16:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/209#comment-14282</guid>
		<description>I&#039;d be interested in your opinion of the infamous list of ELF problems that autopackage posted:
http://trac.autopackage.org/wiki/LinuxProblems</description>
		<content:encoded><![CDATA[<p>I&#8217;d be interested in your opinion of the infamous list of ELF problems that autopackage posted:<br />
<a href="http://trac.autopackage.org/wiki/LinuxProblems" rel="nofollow">http://trac.autopackage.org/wiki/LinuxProblems</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
