<?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 Static Array Allocation in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Static-Array-Allocation/m-p/957915#M21209</link>
    <description>I am converting a 10 year old Scientific Simulation Fortran Program that was developed most recently on MS PowerStation Fortran. It declares a number of large static arrays of real and complex numbers in the main program totaling to approximately 3GB. The program ran fine on all versions of windows and some flavors of UNIX (not sure of the compiler for UNIX).  In all runs of the program, the static arrays were only partially used. The number of elements depended on input parameters for surface dimensions and such. &lt;BR /&gt; &lt;BR /&gt;When I compile it with CVF v6.5, it compiles and links just fine (barring the linker exception for too large a program, which MS PSF gave as well). But, when I run it, the O/S complains that it doesn't have enough virtual memory to execute the program.  &lt;BR /&gt; &lt;BR /&gt;This behavior implies that the MS Powerstation did not allocate the full static array at the outset of the program. Rather, it must have allocated the memory based on access to the array. Pretty neat trick, if that is what it is doing.  &lt;BR /&gt; &lt;BR /&gt;Has anyone come across this behavior before? Do you have any recommendations or workarounds. The obvious modification is to convert the arrays to dynamically allocated to sizes based on the program input parameters.  Any others? &lt;BR /&gt; &lt;BR /&gt;Thanks, &lt;BR /&gt;Bob</description>
    <pubDate>Wed, 11 Jul 2001 01:37:15 GMT</pubDate>
    <dc:creator>Intel_C_Intel</dc:creator>
    <dc:date>2001-07-11T01:37:15Z</dc:date>
    <item>
      <title>Static Array Allocation</title>
      <link>https://community.intel.com/t5/Software-Archive/Static-Array-Allocation/m-p/957915#M21209</link>
      <description>I am converting a 10 year old Scientific Simulation Fortran Program that was developed most recently on MS PowerStation Fortran. It declares a number of large static arrays of real and complex numbers in the main program totaling to approximately 3GB. The program ran fine on all versions of windows and some flavors of UNIX (not sure of the compiler for UNIX).  In all runs of the program, the static arrays were only partially used. The number of elements depended on input parameters for surface dimensions and such. &lt;BR /&gt; &lt;BR /&gt;When I compile it with CVF v6.5, it compiles and links just fine (barring the linker exception for too large a program, which MS PSF gave as well). But, when I run it, the O/S complains that it doesn't have enough virtual memory to execute the program.  &lt;BR /&gt; &lt;BR /&gt;This behavior implies that the MS Powerstation did not allocate the full static array at the outset of the program. Rather, it must have allocated the memory based on access to the array. Pretty neat trick, if that is what it is doing.  &lt;BR /&gt; &lt;BR /&gt;Has anyone come across this behavior before? Do you have any recommendations or workarounds. The obvious modification is to convert the arrays to dynamically allocated to sizes based on the program input parameters.  Any others? &lt;BR /&gt; &lt;BR /&gt;Thanks, &lt;BR /&gt;Bob</description>
      <pubDate>Wed, 11 Jul 2001 01:37:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Static-Array-Allocation/m-p/957915#M21209</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2001-07-11T01:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Static Array Allocation</title>
      <link>https://community.intel.com/t5/Software-Archive/Static-Array-Allocation/m-p/957916#M21210</link>
      <description>None other :-). PSF's ability to create a runnable program looks odd to me -- I wouldn't expect it to work. Namely, 32-bit OS is &lt;B&gt;theoretically&lt;/B&gt; able to work with 2GB of memory; real limit is somewhat lower. But, ALLOCATABLE arrays are a definite recommendation for such kind of problem.</description>
      <pubDate>Wed, 11 Jul 2001 17:26:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Static-Array-Allocation/m-p/957916#M21210</guid>
      <dc:creator>Jugoslav_Dujic</dc:creator>
      <dc:date>2001-07-11T17:26:57Z</dc:date>
    </item>
  </channel>
</rss>

