<?xml version="1.0"?>
<!DOCTYPE flagsdescription
   SYSTEM "http://www.spec.org/dtd/cpuflags1.dtd"
>
<flagsdescription>

<filename>GCC-4.4.0</filename>
<title>SPEC CPU2006 Flag Descriptions for gfortran/gcc</title>

<header><![CDATA[

<h2>Flags descriptions for GCC 4.4.0</h2>

<p id="gnote"><b>Note:</b> The GNU Compiler Collection provides a wide array of compiler options, which are described in
detail in the documentation at 
<a href="http://gcc.gnu.org/onlinedocs/gcc-4.4.0/gcc/Option-Index.html#Option-Index">
http://gcc.gnu.org/onlinedocs/gcc-4.4.0/gcc/Option-Index.html#Option-Index</a>
and <a href="http://gcc.gnu.org/onlinedocs/gcc-4.4.0/gfortran/">http://gcc.gnu.org/onlinedocs/gcc-4.4.0/gfortran/</a>.
The descriptions contained in this SPEC flags file are not intended to replace those documents.  </p>

<p>The experienced reader of SPEC flags files may notice that this file is somewhat less detailed than usual.  The GCC
documentation is (a) very detailed; (b) readily available; and (c) restricted as to requirements if re-formatted, modified,
or re-packaged, per the terms of the <a
href="http://gcc.gnu.org/onlinedocs/gcc/GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU Free
Documentation License</a>.   Out of an abundance of caution, and an abundance of respect, the author of this flags file
prefers to provide briefer summaries here in this flags file, while providing handy links to the more detailed versions.
</p>

<hr />

]]></header>

<platform_settings><![CDATA[

<p><b>numactl</b> <br />It is advantageous to bind a process to a particular core. Otherwise, the OS may arbitrarily move your
process from one core to another.  To help, SPEC allows the use of a "submit" config file option where users can specify a
utility to use to bind processes.  This option is used with the Linux 'numactl' command to  run processes with a specific
NUMA scheduling or memory placement policy. The policy is set for a command and inherited by all of its children. </p>
<ul>
<li>"--physcpubind" specifies which core(s) to bind the process. </li>
<li>"-l" instructs numactl to keep a process memory on the
local node </li>
<li>"-m" specifies which node(s) to place a process memory.  </li>
</ul>


<p><b>Large Pages</b> <br /> Large pages were created using this recipe, which is from the hugetlb HOWTO:</p>
<pre>
sysctl vm.nr_hugepages=512
HUGETLB_MORECORE=yes
export LD_PRELOAD=/usr/lib64/libhugetlbfs.so
</pre>

<p>Setting the sysctl vm.nr_hugepages specifies how many large pages should be reserved.  
As described in <tt>man libhugetlbfs</tt>, the environment variables cause large pages to be allocated for application
memory.  </p>


]]></platform_settings>




<flag name="gxx"
      regexp="g\+\+"
      class="compiler">
<example>g++</example>
<![CDATA[<p>
Invokes the GNU C++ compiler
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="gcc"
      regexp="gcc"
      class="compiler">
<example>gcc</example>
<![CDATA[<p>
Invokes the GNU C compiler
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="gfortran"
      regexp="gfortran"
      class="compiler">
<example>gfortran</example>
<![CDATA[<p>
Invokes the GNU Fortran compiler
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<!--  ========================================================================
-->

<flag name="F-ffast-math"
      class="optimization">
<![CDATA[<p>
Enables a range of optimizations that provide faster, though sometimes less precise, mathematical operations.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-ffixed-form"
      class="other">
<![CDATA[<p>
Allows source code in traditional (fixed-column) Fortran layout.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-fprefetch-loop-arrays" 
      class="optimization">
<![CDATA[<p>
Enables prefetching of arrays used in loops.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-fprofile-generate"
      class="optimization">
<![CDATA[<p>
Instruments code to collect information for profile-driven feedback.
Information is collected regarding both code paths and data values.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-fprofile-use"
      class="optimization">
<![CDATA[<p>
Applies information from a profile run in order to improve optimization.
Several optimizations are improved when profile data is available, including branch probabilities, loop peeling, and loop
unrolling.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="ftree-parallelize-loops"
      regexp="-ftree-parallelize-loops=\d"
      class="optimization">
<![CDATA[<p>
Attempts to decompose loops in order to run them on multiple processors.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-funroll-all-loops"
      class="optimization">
<![CDATA[<p>
Tells the optimizer to unroll all loops. 
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-m64"
      class="optimization">
<![CDATA[<p>
Compiles for a 64-bit (LP64) data model.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-march:core2"
      class="optimization">
<![CDATA[<p>
Allows use of instructions that require the Intel Core2 architecture.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-mtune:core2"
      class="optimization">
<![CDATA[<p>
Tunes code based on the Intel Core2 architecture.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-msse4.2"
      class="optimization">
<![CDATA[<p>
Allows use of instructions that require SSE 4.2 hardware.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>


<flag name="O"
      regexp="-O\d\b"
      class="optimization">
<![CDATA[<p>
Increases optimization levels: the higher the number, the more optimization is done.  Higher levels of optimization may
require additional compilation time, in the hopes of reducing execution time.  At -O, basic optimizations are performed, 
such as constant merging and elimination of dead code.  At -O2, additional optimizations are added, such as common
subexpression elimination and strict aliasing.  At -O3, even more optimizations are performed, such as function inlining and
vectorization.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="F-Wall"
      class="other">
<![CDATA[<p>
Enables warnings.
<br /><a href="#gnote">More details are available</a>.</p>]]>
</flag>

<flag name="Wlzpage"
      regexp='-Wl,-z common-page-size=2M'
      class="optimization">
<example>-Wl,-z common-page-size=2M</example>
<![CDATA[<p>
Add the linker flag that requests use of big (2 MB) pages at run time.  
</p>]]>
</flag>

</flagsdescription>