<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic stack size per thread cilk plus in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742154#M860</link>
    <description>On Linux, the default stack size isto 1MB.&lt;BR /&gt;&lt;BR /&gt;On Windows, the default is taken from the value set by the /STACK linker option for the executable (the .exe file). If not specified, the Windows linker defaults to 1MB.&lt;BR /&gt;&lt;BR /&gt;As Jim noted, you can override these defaultsusing __cilkrts_set_param().&lt;BR /&gt;&lt;BR /&gt; - Barry</description>
    <pubDate>Wed, 18 Jul 2012 14:16:16 GMT</pubDate>
    <dc:creator>Barry_T_Intel</dc:creator>
    <dc:date>2012-07-18T14:16:16Z</dc:date>
    <item>
      <title>stack size per thread cilk plus</title>
      <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742150#M856</link>
      <description>I want to know if there is any way we can change the stack size per cilk thread that will be spawned.</description>
      <pubDate>Tue, 17 Jul 2012 07:06:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742150#M856</guid>
      <dc:creator>amandeepgautam</dc:creator>
      <dc:date>2012-07-17T07:06:07Z</dc:date>
    </item>
    <item>
      <title>stack size per thread cilk plus</title>
      <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742151#M857</link>
      <description>&lt;P&gt;Intel Cilk Plus doesn't work that way.&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="color: blue;"&gt;cilk_spawn&lt;/SPAN&gt;" is a terrible keyword. Except we never found a better one. The &lt;SPAN style="color: blue;"&gt;cilk_spawn&lt;/SPAN&gt; keyword tells the runtime that the continuation (the code after the spawned function) may be stolen by another worker and run in parallel with the spawned function. It gives permission for parallelism. It does &lt;STRONG&gt;not&lt;/STRONG&gt; command it. The Cilk runtime does &lt;STRONG&gt;not&lt;/STRONG&gt; create a thread in response to the &lt;SPAN style="color: blue;"&gt;cilk_spawn&lt;/SPAN&gt; keyword.&lt;/P&gt;&lt;P&gt;When the runtime steals a continuation, it needs a stack to run it on. So it creates a stack, transfersonto the new stack,and starts executing the continuation. When the two strands sync, you continue executing on the leftmost stack; the one that you entered the function on.&lt;/P&gt;
&lt;P&gt;You can set the size of the stacks that the Cilk runtime will create, both when threads are created and when the runtime creates these extra stacks.  But a stack may move between threads.  You don't have control on a per-thread basis.&lt;/P&gt;
&lt;P&gt;- Barry&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jul 2012 13:11:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742151#M857</guid>
      <dc:creator>Barry_T_Intel</dc:creator>
      <dc:date>2012-07-17T13:11:48Z</dc:date>
    </item>
    <item>
      <title>stack size per thread cilk plus</title>
      <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742152#M858</link>
      <description>What you said pretty much answers my question but not I was looking for. I want to know that where does cilk plus runtime takes this stacksize information when it initializes address space for the first time and if we change that configration before starting the program we can have all threads with greater stack size. If I am not clear please tell I will try to explain in more details</description>
      <pubDate>Wed, 18 Jul 2012 01:28:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742152#M858</guid>
      <dc:creator>amandeepgautam</dc:creator>
      <dc:date>2012-07-18T01:28:53Z</dc:date>
    </item>
    <item>
      <title>stack size per thread cilk plus</title>
      <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742153#M859</link>
      <description>&lt;P&gt;At the beginning of "main" in your program (before using any Cilk keywords), try executing the folllowing call, and see if it addresses your problem.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class="sectionBody"&gt; __cilkrts_set_param("stack size", "2000000"); &lt;BR /&gt;&lt;BR /&gt;That should set the default size of all of the stacks that Cilk creates to approximately 2 MB. &lt;BR /&gt;Note that the Cilk runtime creates more than P stacks on amachine with P worker threadsbecause of the way the scheduler works, so use with caution.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Jim&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2012 13:52:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742153#M859</guid>
      <dc:creator>Jim_S_Intel</dc:creator>
      <dc:date>2012-07-18T13:52:16Z</dc:date>
    </item>
    <item>
      <title>stack size per thread cilk plus</title>
      <link>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742154#M860</link>
      <description>On Linux, the default stack size isto 1MB.&lt;BR /&gt;&lt;BR /&gt;On Windows, the default is taken from the value set by the /STACK linker option for the executable (the .exe file). If not specified, the Windows linker defaults to 1MB.&lt;BR /&gt;&lt;BR /&gt;As Jim noted, you can override these defaultsusing __cilkrts_set_param().&lt;BR /&gt;&lt;BR /&gt; - Barry</description>
      <pubDate>Wed, 18 Jul 2012 14:16:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/stack-size-per-thread-cilk-plus/m-p/742154#M860</guid>
      <dc:creator>Barry_T_Intel</dc:creator>
      <dc:date>2012-07-18T14:16:16Z</dc:date>
    </item>
  </channel>
</rss>

