<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated on Fri, 25 May 2012 23:05:43 -0700 -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="http://software.intel.com/en-us/articles/visualizing-parallel-speedup-with-cilkview/feed/" rel="self" type="application/rss+xml" />
    <title>Intel Software Network Comments Feed</title>
    <link>http://software.intel.com/en-us/articles/visualizing-parallel-speedup-with-cilkview</link>
    <description></description>
    <language>en-us</language>
    <item>
      <title>By Ryan Newton</title>
      <description><![CDATA[ Hi Will,

I'm trying to understand why this required a pintool.  It looks like you need to recompile the app anyway (#include <cilkview.h>).  And ultimately what you need to get out of the application is the DAG plus reading the cycle counter at the start end of serial regions between cilk operations (spawn sync), right?

There would certainly be overhead to logging all that, but it seems doable just by changing mode within libcilkrts.  So what am I missing?  Is the problem just the extra complexity -- is there anything here that would require modifying the C compiler (to change the generated code for spawns)?

Thanks,
  -Ryan
 ]]></description>
      <link>http://software.intel.com/en-us/articles/visualizing-parallel-speedup-with-cilkview/#comment-72107</link>
      <pubDate>Tue, 27 Mar 2012 06:50:24 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/visualizing-parallel-speedup-with-cilkview/#comment-72107</guid>
    </item>
  </channel></rss>
