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

<flagsdescription>
<filename>fsc-mix-pgi-path.xml</filename>
<title>Flag Description for Fujitsu Siemens Siemens Computers</title>


<!-- Style -->

<style>
<![CDATA[
body {
  margin:  1em;
  border:  0;
  padding: 0;
  background-repeat: no-repeat;
  background-attachment: fixed;
  background-position: 100% 0;
  color:      black;
  font-family: "Times Roman", times, serif;
}

div.flagDesc {
  clear: both;
  color: black;
  background-color: #d6e7f7;
  border: 1px solid #blue;
  margin: 0 auto;
  width: 90%;
}

ul.flagTOC {
  list-style-type: none;
  margin: 0;
  padding: 0;
}

ul.flagTOC > li {
  border: 1px solid #d6e7f7;
  background: #d6e7f7;
}

ul.flagTOC > li > a:link {
   color: blue;
}

ul.SubMenu li {
  border: 1px solid #d6e7f7; /* rgb(211, 211, 211); */
}

ul.SubMenu {
  border: 1px solid blue;
  background-color: #d6e7f7;
}
]]>
</style>

<!-- Header -->

<header>
<![CDATA[
   <div id='banner'>
   <h2><b>Compilers: PGI Workstation Complete 7.2
   and PathScale Compiler Suite 3.2</b></h2>
   <h2><b>Operating system: Linux</b></h2>
   </div>
   Copyright &copy; 2008 The Portland Group, Inc. (for PGI compilers)<br>
   Copyright &copy; 2008 PathScale LLC (for PathScale Compiler Suite)
]]>
</header>

<!-- Platform Settings -->
<platform_settings>
<![CDATA[
      <p>One or more of the following settings may have been set.
      If so, the corresponding notes sections of the report will say so;
      and you can read below to find out more about what these settings mean.
      </p>

      <p><b><font size="4">Environment Variables</font></b></p>

      <p><b>MP_BIND</b></p>
      <p>This Environment Variable controls the runtime behavior
      of binaries compiled with the PGI compilers.<br>
      It can be set to yes or y
      to bind processes or threads executing in a parallel region
      to physical processors, or to no or n to disable such binding.
      The default is to not bind processes to processors.<br>
      This is an execution time environment variable interpreted by the
      PGI runtime support libraries. It does not affect the behavior
      of the PGI compilers in any way. Note: the MP_BIND
      environment variable is not supported on all platforms.
      </p>

      <p><b>MP_BLIST</b></p>
      <p>This Environment Variable controls the runtime behavior
      of binaries compiled with the PGI compilers.<br>
      In addition to the MP_BIND variable, it is possible to define
      the thread-CPU relationship.
      For example, setting MP_BLIST=3,2,1,0 maps CPUs 3, 2, 1 and 0
      to threads 0, 1, 2 and 3 respectively.
      </p>

      <p><b>OMP_NUM_THREADS</b></p>
      <p>This Environment Variable controls the runtime behavior
      of binaries compiled with the PGI and PathScale compilers.<br>
      This Environment Variable
      sets the maximum number of threads to use for OpenMP* parallel regions
      if no other value is specified in the application.
      This environment variable applies to both -openmp and -parallel
      (Linux and Mac OS X) or /Qopenmp and /Qparallel (Windows).
      Example syntax on a Linux system with 8 cores:<br>
      export OMP_NUM_THREADS=8<br>
      Default is the number of cores visible to the OS.</p>

      <p><b>PGI_HUGE_PAGES</b></p>
      <p>This Environment Variable controls the runtime behavior
      of binaries compiled with the PGI compilers.<br>
      The maximum number of huge pages an application is allowed
      to use can be set at run time via the environment variable
      PGI_HUGE_PAGES.  If not set, then the process may use all
      available huge pages when compiled with "-Msmartalloc=huge"
      or a maximum of <b>n</b> pages where the value of <b>n</b>
      is set via the compile time flag "-Msmartalloc=huge:<b>n</b>."
      </p>

      <p><b>KMP_AFFINITY </b></p>
      <p>
      KMP_AFFINITY  = &lt; physical | logical &gt;, starting-core-id <br/>
      This Environment Variable
      specifies the static mapping of user threads to physical cores,
      for example, if you have a system
      configured with 8 cores, OMP_NUM_THREADS=8 and KMP_AFFINITY=physical,2.
      Thread 0 will mapped to core 2, thread 1 will be mapped to core 3, and
      so on in a round-robin fashion.
      </p>

      <p><b><font size="4">Linux commands</font></b></p>

      <p><b>ulimit -s &lt; n | unlimited &gt;</b></p>
      <p>
      This Linux command (a bash builtin command)
      sets the stack size to <b>n</b> kbytes, or <b>unlimited</b>
      to allow the stack size to grow without limit.
      </p>

      <p><b>ulimit -l &lt; n | unlimited &gt;</b></p>
      <p>
      This Linux command (a bash builtin command)
      sets the maximum size of memory that may be locked
      into physical memory.</p>

      <p><b>numactl -m nodes --physcpubind=cpus command</b></p>
      <p>
      numactl runs processes with a specific NUMA scheduling or memory placement 
		policy. The policy is set for <i>command</i> and inherited by all of its 
		children. The arguments used here are:</p>
       <ul>
	<li><b>-m nodes</b><br>
	Only allocate memory from<i> nodes</i>. Allocation will fail when there is 
	not enough memory available on these nodes.
	Synonym:<i> </i><b>--membind nodes</b></li>
	<li><b>--physcpubind=cpus</b><br>
	Only execute process on<i> cpus</i>. This accepts physical cpu numbers as 
	shown in the <i>processor</i> fields of <i>/proc/cpuinfo</i>. Synonym: <b>-C 
	cpus</b></li>
	<li><b>command</b><br>
	Command to be executed under control of numactl.</li>
       </ul>
      <p>numactl has many more options which are not described here since they are not 
      used.</p>

      <p>
      <b>
      <font size="4">SPEC config file feature submit</font></b>
      </p>

      <p><b>submit = echo &quot;$command&quot; &gt;run.sh ; $BIND bash run.sh</b></p>
      <p>When running multiple copies of benchmarks, the SPEC config file feature
      <b>submit</b> is sometimes used to cause individual jobs to be bound to
      specific processors. This specific submit command is used for Linux.
      The description of the elements of the command are:
      </p>
      <ul>
         <li><b>$command</b><br>
            Program to be started. In this case, the benchmark instance to be started.
         </li>
		<li><b>echo &quot;$command&quot; &gt;run.sh</b><br>
            The Linux command <i>echo</i> is used to write the command to be 
			executed into the file <i>run.sh</i>.
		 </li>
         <li><b>bash run.sh</b><br>
            Execute the commands in file<i> run.sh</i> with the bash shell.
         </li>
         <li><b>$BIND</b><br>
            Use a value from your bind list. This variable is 
			actually interpreted by specinvoke.
		 </li>
		 <li><b>bind list (contained in config file)</b><br>
            List of values with which $BIND should be replaced in a submit command. For example, the following 
			list gives good results with a 2-chip quad-core configuration.<br>
<pre>bind0 = numactl -m 0 --physcpubind=0
bind1 = numactl -m 0 --physcpubind=1
bind2 = numactl -m 0 --physcpubind=2
bind3 = numactl -m 0 --physcpubind=3
bind4 = numactl -m 1 --physcpubind=4
bind5 = numactl -m 1 --physcpubind=5
bind6 = numactl -m 1 --physcpubind=6
bind7 = numactl -m 1 --physcpubind=7
</pre>
			<p class="snugbot">In this example, the first benchmark instance 
			uses bind0, so &quot;$BIND bash runsh&quot; is expanded to become &quot;numactl -m 
			0 --physcpubind=0 bash run.sh&quot;. The second instance uses bind1, and 
			so on.<br>
			If there are more copies than bind values, they 
			will be re-used in a circular fashion. If there are more bind values 
			specified than copies, then only as many as needed will be used.</li>
      </ul>
      </p>

<p><b><font size="4">Linux Huge Page settings</font></b></p>
<p>In order to take full advantage of using PGI's huge page runtime library, your system must be configured to use huge pages.
It is safe to run binaries compiled with "-Msmartalloc=huge" on systems not configured to use huge pages, however, you will not
benefit from the performance improvements huge pages offer.  To configure your system for huge pages perform the following steps:
</p>
<ul>
      <li>Create a mount point for the huge pages: "mkdir /mnt/hugepages"</li>
      <li>The huge page file system needs to be mounted when the systems reboots.  Add the following to a system boot configuration file before any services are started: "mount -t hugetlbfs nodev /mnt/hugepages"</li>
      <li>Set vm/nr_hugepages=N in your /etc/sysctl.conf file where N is the maximum number of pages the system may allocate.</li>
      <li>Reboot to have the changes take effect.</li>
		<li>If desired, use the Environment Variable PGI_HUGE_PAGES to control 
		the run-time behavior.</li>
</ul>
<p>Note that further information about huge pages may be found
in your Linux documentation file: /usr/src/linux/Documentation/vm/hugetlbpage.txt</p>
   ]]>
</platform_settings>



<!-- Compilers -->

   <flag name='C_PGI' class='compiler' regexp="pgcc\b" >
      <![CDATA[
         <p>Invoke the PGI C compiler.<br>
         Also used to invoke linker for C programs.</p>
      ]]>
      <example>pgcc</example>
   </flag>

   <flag name='Cplusplus_PGI' class='compiler' regexp="pgcpp\b">
      <![CDATA[
         <p>Invoke the PGI C++ compiler.<br>
         Also used to invoke linker for C++ programs.</p>
      ]]>
      <example>pgcpp</example>
   </flag>

   <flag name='Fortran_PGI' class='compiler' regexp="pgf95\b" >
      <![CDATA[
         <p>Invoke the PGI Fortran 95 compiler.<br>
         Also used to invoke linker for Fortran programs and
         for mixed C / Fortran.</p>
      ]]>
      <example>pgf95</example>
   </flag>

   <flag name="C_PathScale" class="compiler" regexp="pathcc\b">
      <example>pathcc</example>
      <![CDATA[
         <p>Invoke the PathScale C compiler.<br>
         Also used to invoke linker for C programs.</p>
      ]]>
   </flag>

   <flag name="Cplusplus_PathScale" class="compiler" regexp="pathCC\b">
      <example>pathCC</example>
      <![CDATA[
         <p>Invoke the PathScale C++ compiler.<br>
         Also used to invoke linker for C++ programs.</p>
      ]]>
   </flag>

   <flag name="Fortran_PathScale" class="compiler" regexp="pathf95\b">
      <example>pathf95</example>
      <![CDATA[
         <p>Invoke the PathScale Fortran 77, 90 and 95 compilers.<br>
         Also used to invoke linker for Fortran programs and
         for mixed C / Fortran.  pathf90 and pathf95 are synonymous.</p>
      ]]>
   </flag>

<!-- /COMPILER -->

<!-- Portability, Other Flags. -->

   <flag name="w" class="other"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI" regexp="-w\b">
      <![CDATA[
         <p>Disable warning messages.</p>
      ]]>
      <example>-w</example>
   </flag>

   <flag name="Mnomain" class="portability"
      compilers="Fortran_PGI"
      regexp="-Mnomain\b">
      <![CDATA[
         <p>Don't include Fortran main program object module.</p>
      ]]>
      <example>-Mnomain</example>
   </flag>

   <flag name="c9x" class="optimization"
      compilers="C_PGI" regexp="-c9x\b">
      <![CDATA[
         <p>Use C99 language features.</p>
      ]]>
      <example>-c9x</example>
   </flag>

   <flag name="F-fno-second-underscore" class="portability">
      <example>-fno-second-underscore</example>
      <![CDATA[
         <p><b>CFP2006:</b></p>
         <p>If  -funderscoring is in effect, and the original Fortran external
         identifier contained an underscore, -fsecond-underscore appends
         a second underscore to  the one added  by  -funderscoring.
         -fno-second-underscore  does  not append a second underscore.
         The default is both -funderscoring and -fsecond-underscore, the
         same defaults as g77 uses.  -fno-second-underscore corresponds
         to the default policies of PGI Fortran and Intel Fortran.

      ]]>
   </flag>

<!-- Optimization Flags -->

<flag name="fast"
  class="optimization"
  compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
  regexp="-fasts?s?e?\b">
<![CDATA[
 <p>Chooses generally optimal flags for the target platform.  As of the PGI 7.0 release, the flags "-fast"
and "-fastsse" are equivlent for 64-bit compilations.  For 32-bit compilations "-fast" does not include
"-Mscalarsse", "-Mcache_align", or "-Mvect=sse".</p>
 ]]>
<example>-fast</example>
<include flag="O2" />
<include flag="Munroll_c_n" flagtext="-Munroll=c:1" />
<include flag="Mautoinline" />
<include flag="Msmart" />
<include flag="Mlre" />
<include flag="Mnoframe" />
<include flag="Mvect_sse" />
<include flag="Mcache_align" />
<include flag="Mflushz" />
<include flag="Mdaz" />
<include flag="Mscalarsse" />
</flag>

<flag name="no-exceptions"
 class="optimization"
 compilers="Cplusplus_PGI"
 regexp="--no_exceptions\b">
<![CDATA[
 <p>Disable C++ exception handling support.</p>
 ]]>
<example>--no_exceptions</example>
</flag>

<flag name="no-rtti"
 class="optimization"
 compilers="Cplusplus_PGI"
 regexp="--no_rtti\b">
<![CDATA[
 <p>Disable C++ run time type information support.</p>
 ]]>
<example>--no_rtti</example>
</flag>

<flag name="zc_eh" class="optimization"
 compilers="Cplusplus_PGI"
 regexp="--zc_eh\b">
<![CDATA[
<p>Generate zero-overhead C++ exception handlers.</p>
]]>
</flag>

<flag name="Mautoinline"
 class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mautoinline\b">
<![CDATA[
<p>Inline functions declared with the inline keyword.</p>
]]>
<example>-Mautoinline</example>
</flag>

<flag name="Mnoautoinline"
 class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnoautoinline\b">
<![CDATA[
<p>Disable inlining of functions declared with the inline keyword.</p>
]]>
<example>-Mnoautoinline</example>
</flag>


<flag name="Mcache_align"
 class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mcache_align\b">
<![CDATA[
 <p>Align "unconstrained" data objects of size greater than or equal to 16
bytes on cache-line boundaries.  An "unconstrained" object is a variable or
array that is not a member of an aggregate structure or common block, is not
allocatable, and is not an automatic array.  On by default on 64-bit Linux systems.</p>
 ]]>
<example>-Mcache_align</example>
</flag>

<flag name="Mdalign"
  class="optimization"
  compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
  regexp="-Mdalign\b">
<![CDATA[
 <p>Align doubles on double alignment boundaries</p>
]]>
<example>-Mdalign</example>
</flag>

<flag name="Mnodalign"
  class="optimization"
  compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
  regexp="-Mnodalign\b">
<![CDATA[
 <p>Do not align doubles on double alignment boundaries</p>
]]>
<example>-Mnodalign</example>
</flag>

<flag name="Mflushz"
  class="optimization"
  compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
  regexp="-Mflushz\b">
<![CDATA[
 <p>Set SSE to flush-to-zero mode; if a floating-point underflow occurs, the value is set to zero.</p>
]]>
<example>-Mflushz</example>
</flag>

<flag name="Mdaz"
  class="optimization"
  compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
  regexp="-Mdaz\b">
<![CDATA[
 <p>Treat denormalized numbers as zero.  Included with "-fast" on Intel based systems.  For AMD based systems, "-Mdaz" is
not included by default with "-fast".</p>
]]>
<example>-Mdaz</example>
</flag>

<flag name="Mframe" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mframe\b">
<![CDATA[
 <p>Generate code to set up a stack frame.</p>
]]>
<example>-Mframe</example>
</flag>

<flag name="Mnoframe" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnoframe\b">
<![CDATA[
 <p>Eliminates operations that set up a true stack frame pointer for every function.  With this option enabled, you
cannot perform a traceback on the generated code and you cannot access local variables.</p>
]]>
<example>-Mnoframe</example>
</flag>

<flag name="Mfprelaxed_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mfprelaxed=([^,\s]+),(\S+)\b" >
<include text="-Mfprelaxed=$1" />
<include text="-Mfprelaxed=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mfprelaxed_rsqrt" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfprelaxed=rsqrt\b">
<![CDATA[
 <p>Instructs the compiler to use relaxed precision in the calculation of floating-point reciprocal square root (1/sqrt). Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfprelaxed=rsqrt</example>
</flag>

<flag name="Mfprelaxed_sqrt" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfprelaxed=sqrt\b">
<![CDATA[
 <p>Instructs the compiler to use relaxed precision in the calculation of floating-point square root. Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfprelaxed=sqrt</example>
</flag>

<flag name="Mfprelaxed_div" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfprelaxed=div\b">
<![CDATA[
 <p>Instructs the compiler to use relaxed precision in the calculation of floating-point division. Can result in improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfprelaxed=div</example>
</flag>

<flag name="Mfprelaxed_order" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfprelaxed=order\b">
<![CDATA[
 <p>Instructs the compiler to allow floating-point expression reordering, including factoring. Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfprelaxed=order</example>
</flag>

<flag name="Mfprelaxed" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfprelaxed\b">
<![CDATA[
 <p>Instructs the compiler to use relaxed precision in the calculation of some intrinsic functions.  Can result in
improved performance at the expense of numerical accuracy.  The default on an AMD system is "-Mfprelaxed=sqrt,rsqrt,order".  The
default on an Intel system is "-Mfprelaxed=rsqrt,sqrt,div,order"</p>
 ]]>
<example>-Mfprelaxed</example>
<include flag="Mfprelaxed_rsqrt" />
<include flag="Mfprelaxed_sqrt" />
<include flag="Mfprelaxed_div" />
<include flag="Mfprelaxed_order" />
</flag>


<flag name="Mfpapprox_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mfpapprox=([^,\s]+),(\S+)\b" >
<include text="-Mfpapprox=$1" />
<include text="-Mfpapprox=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mfpapprox_rsqrt" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfpapprox=rsqrt\b">
<![CDATA[
 <p>Instructs the compiler to use low-precision approximation in the calculation of reciprocal square root (1/sqrt). Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfpapprox=rsqrt</example>
</flag>

<flag name="Mfpapprox_sqrt" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfpapprox=sqrt\b">
<![CDATA[
 <p>Instructs the compiler to use low-precision approximation in the calculation of square root. Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfpapprox=sqrt</example>
</flag>

<flag name="Mfpapprox_div" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfpapprox=div\b">
<![CDATA[
 <p>Instructs the compiler to use low-precision approximation in the calculation of divides.  Can result in
improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfpapprox=div</example>
</flag>

<flag name="Mfpapprox" class="optimization"
      compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
      regexp="-Mfpapprox\b">
<![CDATA[
 <p>Instructs the compiler to perform low-precision approximation in the calculation of floating-point division, square-root, and reciprocal square root.
Can result in improved performance at the expense of numerical accuracy.</p>
 ]]>
<example>-Mfpapprox</example>
<include flag="Mfpapprox_rsqrt" />
<include flag="Mfpapprox_sqrt" />
<include flag="Mfpapprox_div" />
</flag>


<flag name="Mpre_all" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpre=all\b" >
<![CDATA[
Enable aggressive partial redundancy elimination.
 ]]>
<example>-Mpre</example>
</flag>

<flag name="Mpre" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpre\b" >
<![CDATA[
Enable partial redundancy elimination.
 ]]>
<example>-Mpre</example>
</flag>

<flag name="Mprefetch_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=([^,\s]+),(\S+)\b" >
<include text="-Mprefetch=$1" />
<include text="-Mprefetch=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mprefetch_d_m" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=d[istance]*:(\d+)\b">
<![CDATA[
 <p>Set the fetch-ahead distance for prefetch instructions to <b>$1</b> cache lines</p>
]]>
<example>-Mprefetch=d:m</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch_n_p" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=n:(\d+)\b">
<![CDATA[
 <p>Set maximum number of prefetch instructions to generate for a given loop to <b>$1</b>.</p>
]]>
<example>-Mprefetch=n:p</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch_nta" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=nta\b">
<![CDATA[
 <p>Use the <i>prefetchnta</i> instruction.</p>
]]>
<example>-Mprefetch_nta</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch_plain" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=plain\b">
<![CDATA[
 <p>Use the <i>prefetch</i> instruction.</p>
]]>
<example>-Mprefetch=plain</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch_t0" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=t0\b" >
<![CDATA[
 <p>Use the <i>prefetcht0</i> instruction.</p>
]]>
<example>-Mprefetch=t0</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch_w" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch=w\b" >
<![CDATA[
 <p>Use the AMD-specific <i>prefetchw</i> instruction.</p>
]]>
<example>-Mprefetch=w</example>
<include flag="Mprefetch" />
</flag>

<flag name="Mprefetch" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mprefetch\b">
<![CDATA[
 <p>Enable generation of prefetch instructions on processors where they are supported.</p>
]]>
<example>-Mprefetch</example>
</flag>

<flag name="Mnoprefetch" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnoprefetch\b" >
<![CDATA[
 <p>Disable generation of prefetch instructions.</p>
]]>
<example>-Mnoprefetch</example>
</flag>

<flag name="Mscalarsse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mscalarsse\b">
<![CDATA[
 <p>Use SSE/SSE2 instructions to perform scalar floating-point arithmetic on targets where these
 instructions are supported.</p>
]]>
<example>-Mscalarsse</example>
</flag>

<flag name="Mnoscalarsse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnoscalarsse\b">
<![CDATA[
 <p>Do not use SSE/SSE2 instructions to perform scalar floating-point arithmetic; use x87 operations instead.</p>
]]>
<example>-Mnoscalarsse</example>
</flag>

<flag name="Msignextend" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msignextend\b">
<![CDATA[
 <p>Instructs the compiler to extend the sign bit that is set as a result of an object's conversion from one
 data type to an object of a larger signed data type.</p>
]]>
<example>-Msignextend</example>
</flag>

<flag name="Mloop32" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mloop32\b">
<![CDATA[
 <p>Aligns or does not align innermost loops on 32 byte boundaries with -tp barcelona.
Small loops on barcelona systems may run fast if aligned on 32-byte boundaries; however, in practice, most
assemblers do not yet implement efficient padding causing some programs to run more slowly with this as
default. Use -Mloop32 on systems with an assembler tuned for barcleona. The default is -Mnoloop32.
</p>
]]>
<example>-Mloop32</example>
</flag>

<flag name="Mlre_array" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlre=array\b">
<![CDATA[
 <p>Treat individual array element references as candidates for possible loop-carried redundancy elimination.
 The default is to eliminate only redundant expressions involving two or more operands.</p>
]]>
<example>-Mlre_array</example>
<include flag="Mlre" />
</flag>

<flag name="Mlre_assoc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlre=assoc\b">
<![CDATA[
 <p>Allow expression re-association; specifying this sub-option can increase opportunities for loop-carried
 redundancy elimination.</p>
]]>
<example>-Mlre=assoc</example>
<include flag="Mlre" />
</flag>

<flag name="Mlre_noassoc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlre=noassoc\b">
<![CDATA[
 <p>Disable expression re-association.</p>
]]>
<example>-Mlre=noassoc</example>
<include flag="Mlre" />
</flag>

<flag name="Mlre" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlre\b">
<![CDATA[
 <p>Enables loop-carried redundancy elimination, an optimization that can reduce the number of arithmetic operations
 and memory references in loops.</p>
]]>
<example>-Mlre</example>
</flag>

<flag name="Mnolre" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnolre\b">
<![CDATA[
 <p>Disable loop-carried redundancy elimination.</p>
]]>
<example>-Mnolre</example>
</flag>

<flag name="Mnovintr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnovintr\b">
<![CDATA[
 <p>Instructs the compiler not to perform idiom recognition or introduce calls to hand-optimized vector functions.</p>
]]>
<example>-Mnovintr</example>
</flag>

<flag name="Mpfi_indirect" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpfi=indirect\b">
<![CDATA[
 <p>Generate profile-feedback instrumentation (PFI); this includes extra code to collect run-time statistics and dump
 them to a trace file for use in a subsequent compilation.  PFI gathers information about a program's execution and data values
but does not gather information from hardware performance counters.  PFI does gather data for optimizations which are unique to profile-feedback optimization.</p>
<p>The indirect sub-option enables collection of indirect function call targets, which can be used for indirect function call inlining.</p>
]]>
<example>-Mpfi=indirect</example>
</flag>

<flag name="Mpfo_indirect" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpfo=indirect\b">
<![CDATA[
 <p>Enable profile-feedback optimizations including indirect function call inlining.  This option requires a pgfi.out file generated from a binary built with -Mpfi=indirect.</p>
]]>
<example>-Mpfo=indirect</example>
</flag>

<flag name="Mpfi" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpfi\b">
<![CDATA[
 <p>Generate profile-feedback instrumentation (PFI); this includes extra code to collect run-time statistics and dump
 them to a trace file for use in a subsequent compilation.  PFI gathers information about a program's execution and data values
but does not gather information from hardware performance counters.  PFI does gather data for optimizations which are unique to profile-feedback optimization.</p>
]]>
<example>-Mpfi</example>
</flag>

<flag name="Mpfo" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mpfo\b">
<![CDATA[
 <p>Enable profile-feedback optimizations.  </p>
]]>
<example>-Mpfo</example>
</flag>


<flag name="Mipa_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=([^,\s]+),(\S+)\b">
<include text="-Mipa=$1" />
<include text="-Mipa=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mipa_align" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=align\b">
<![CDATA[
 <p>Interprocedural Analysis option: Recognize when targets of pointer dummy are aligned.</p>
]]>
<example>-Mipa=align</example>
</flag>

<flag name="Mipa_noalign" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noalign\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable recognizition when targets of pointer dummy are aligned.</p>
]]>
<example>-Mipa=noalign</example>
</flag>

<flag name="Mipa_arg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=arg\b">
<![CDATA[
 <p>Interprocedural Analysis option: Remove arguments replaced by -Mipa=ptr,const</p>
]]>
<include flag="Mipa_ptr" />
<include flag="Mipa_const" />
<example>-Mipa=arg</example>
</flag>

<flag name="Mipa_noarg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noarg\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not remove arguments replaced by -Mipa=ptr,const</p>
]]>
<include flag="Mipa_ptr" />
<include flag="Mipa_const" />
<example>-Mipa=noarg</example>
</flag>

<flag name="Mipa_cg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=cg\b">
<![CDATA[
 <p>Interprocedural Analysis option: Generate call graph information for pgicg tool.</p>
]]>
<example>-Mipa=cg</example>
</flag>

<flag name="Mipa_nocg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nocg\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not generate call graph information for pgicg
 tool.</p>
]]>
<example>-Mipa=nocg</example>
</flag>

<flag name="Mipa_const" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=const\b">
<![CDATA[
 <p>Interprocedural Analysis option: Enable interprocedural constant propagation.</p>
]]>
<example>-Mipa=const</example>
</flag>

<flag name="Mipa_noconst" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noconst\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable interprocedural constant propagation.</p>
]]>
<example>-Mipa=noconst</example>
</flag>

<flag name="Mipa_except" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=except:([\-\w,]+)\b">
<![CDATA[
 <p>Interprocedural Analysis option: Used with -Mipa=inline to specify functions which should not be inlined.</p>
]]>
<include flag="Mipa_inline" />
<example>-Mipa=except:func</example>
</flag>

<flag name="Mipa_fast" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=fast\b">
<![CDATA[
 <p>Instructs the compiler to perform interprocedural analysis.  Equivalant to -Mipa=align,arg,const,f90ptr,shape,globals,libc,localarg,ptr,pure.</p>
]]>
<example>-Mipa=fast</example>
<include flag="Mipa_align" />
<include flag="Mipa_arg" />
<include flag="Mipa_const" />
<include flag="Mipa_f90ptr" />
<include flag="Mipa_shape" />
<include flag="Mipa_globals" />
<include flag="Mipa_libc" />
<include flag="Mipa_localarg" />
<include flag="Mipa_ptr" />
<include flag="Mipa_pure" />
</flag>

<flag name="Mipa_force" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=force\b" >
<![CDATA[
 <p>Interprocedural Analysis option: Force all objects to recompile regardless
 whether IPA information has changed.</p>
]]>
<example>-Mipa=force</example>
</flag>

<flag name="Mipa_globals" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=globals\b">
<![CDATA[
 <p>Interprocedural Analysis option: Optimize references to global values.</p>
]]>
<example>-Mipa=globals</example>
</flag>

<flag name="Mipa_noglobals" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noglobals\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not optimize references to global values.</p>
]]>
<example>-Mipa=noglobals</example>
</flag>

<flag name="Mipa_inline:n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=inline:(\d+)\b">
<![CDATA[
 <p>Interprocedural Analysis option: Automatically determine which functions
 to inline, limit to <b>$1</b> levels where <b>$1</b> is a supplied constant value.  If no value is suppiled, then the default value of 2 is used.  IPA-based function inlining is performed from leaf routines upward.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Mipa=inline:4</example>
</flag>

<flag name="Mipa_inline" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=inline\b">
<![CDATA[
 <p>Interprocedural Analysis option: Automatically determine which functions to inline, limit to 2 levels (default).
 IPA-based function inlining is performed from leaf routines upward.</p>
]]>
<example>-Mipa=inline</example>
</flag>

<flag name="Mipa_inlineonpfo:n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=inlinenopfo:(\d+)\b">
<![CDATA[
 <p>Interprocedural Analysis option: Automatically determine which functions
 to inline, independent of information gathered from profile guided feedback (-Mpfi), limit to <b>$1</b> levels where <b>$1</b> is a supplied constant value.  If no value is suppiled, then the default value of 2 is used.  IPA-based function inlining is performed from leaf routines upward.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Mipa=inlinenopfo:4</example>
</flag>

<flag name="Mipa_inlinenopfo" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=inlinenopfo\b">
<![CDATA[
 <p>Interprocedural Analysis option: Automatically determine which functions to inline, independent of information gathered from profile guided feedback (-Mpfi), limit to 2 levels (default).
 IPA-based function inlining is performed from leaf routines upward.</p>
]]>
<example>-Mipa=inlinenopfo</example>
</flag>

<flag name="Mipa_staticfunc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=staticfunc\b">
<![CDATA[
 <p>Interprocedural Analysis option: Inline static functions which are outside the scope of the current file.</p>
]]>
<example>-Mipa=staticfunc</example>
</flag>

<flag name="Mipa_libinline" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=libinline\b">
<![CDATA[
 <p>Interprocedural Analysis option: Allow inlining of routines from libraries.</p>
]]>
<include flag="Mipa_inline" />
<example>-Mipa=libinline</example>
</flag>

<flag name="Mipa_nolibinline" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nolibinline\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not inline routines from libraries.</p>
]]>
<include flag="Mipa_inline" />
<example>-Mipa=nolibinline</example>
</flag>

<flag name="Mipa_jobs" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=jobs:\d\b">
<![CDATA[
 <p>Interprocedural Analysis option:  Specifies the number of concurent IPA second pass compliation proccess that may be performed.  This option speeds-up the compilation time on multi-core systems but does not perform any optimizations.</p>
]]>
<example>-Mipa=libc</example>
</flag>

<flag name="Mipa_libc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=libc\b">
<![CDATA[
 <p>Interprocedural Analysis option:  Used to optimize calls to certain functions in the system standard C library, libc.</p>
]]>
<example>-Mipa=libc</example>
</flag>

<flag name="Mipa_libopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=libopt\b">
<![CDATA[
 <p>Interprocedural Analysis option: Allow recompiling and optimization of routines from libraries using IPA information.</p>
]]>
<example>-Mipa=libopt</example>
</flag>

<flag name="Mipa_nolibopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nolibopt\b">
<![CDATA[
 <p>Interprocedural Analysis option: Don't optimize routines in libraries.</p>
]]>
<example>-Mipa=nolibopt</example>
</flag>

<flag name="Mipa_localarg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=localarg\b">
<![CDATA[
 <p>Interprocedural Analysis option: -Mipa=arg plus externalizes local pointer targets.</p>
]]>
<include flag="Mipa_arg" />
<example>-Mipa=localarg</example>
</flag>

<flag name="Mipa_local" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=local\b">
<![CDATA[
 <p>Interprocedural Analysis option: -Mipa=arg plus externalizes local pointer targets.</p>
]]>
<include flag="Mipa_arg" />
<example>-Mipa=localarg</example>
</flag>

<flag name="Mipa_nolocalarg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nolocal[arg]*\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not externalize local pointer targets.</p>
]]>
<example>-Mipa=nolocalarg</example>
</flag>

<flag name="Mipa_ptr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=ptr\b">
<![CDATA[
 <p>Interprocedural Analysis option: Enable pointer disambiguation across procedure calls.</p>
]]>
<example>-Mipa=ptr</example>
</flag>

<flag name="Mipa_noptr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noptr\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable pointer disambiguation.</p>
]]>
<example>-Mipa=noptr</example>
</flag>

<flag name="Mipa_f90ptr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=f90ptr\b">
<![CDATA[
 <p>Interprocedural Analysis option: Fortran 90/95 Pointer disambiguation across calls.</p>
]]>
<example>-Mipa=f90ptr</example>
</flag>

<flag name="Mipa_nof90ptr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nof90ptr\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable Fortran 90/95 pointer disambiguation</p>
]]>
<example>-Mipa=nof90ptr</example>
</flag>

<flag name="Mipa_pure" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=pure\b">
<![CDATA[
 <p>Interprocedural Analysis option: Pure function detection.</p>
]]>
<example>-Mipa=pure</example>
</flag>

<flag name="Mipa_nopure" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=nopure\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable pure function detection.</p>
]]>
<example>-Mipa=nopure</example>
</flag>

<flag name="Mipa_reshape" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=reshape\b">
<![CDATA[
 <p>Interprocedural Analysis option: Allows inlining in Fortran even when array shapes do not match.</p>
]]>
<example>-Mipa=reshape</example>
</flag>

<flag name="Mipa_shape" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=shape\b">
<![CDATA[
 <p>Interprocedural Analysis option: Perform Fortran 90 array shape propagation.</p>
]]>
<example>-Mipa=shape</example>
</flag>

<flag name="Mipa_noshape" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=noshape\b">
<![CDATA[
 <p>Interprocedural Analysis option: Disable Fortran 90 array shape propagation.</p>
]]>
<example>-Mipa=noshape</example>
</flag>

<flag name="Mipa_vestigial" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=vestigial\b">
<![CDATA[
 <p>Interprocedural Analysis option: Remove functions that are never called.</p>
]]>
<example>-Mipa=vestigial</example>
</flag>

<flag name="Mipa_novestigial" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa=novestigial\b">
<![CDATA[
 <p>Interprocedural Analysis option: Do not remove functions that are never called.</p>
]]>
<example>-Mipa=novestigial</example>
</flag>

<flag name="Mipa" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mipa\b">
<![CDATA[
 <p>Enable Interprocedural Analysis.</p>
]]>
<include flag="Mipa_const" />
<example>-Mipa</example>
</flag>

<flag name="Mconcur_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=([^,\s]+),(\S+)\b">
<include text="-Mconcur=$1" />
<include text="-Mconcur=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mconcur_altcode" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=altcode\b">
<![CDATA[
 <p>Instructs the parallelizer to generate alternate serial code for parallelized loops.  Without arguments,
 the parallelizer determines an appropriate cutoff length and generates serial code to be executed whenever
 the loop count is less than or equal to that length.</p>
]]>
<example>-Mconcur=altcode</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_altcoden" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=altcode:(\d+)\b">
<![CDATA[
 <p>Instructs the parallelizer to generate alternate serial code for parallelized loops.  With arguments, the serial altcode
 is executed whenever the loop count is less than or equal to <b>$1</b>.</p>
]]>
<example>-Mconcur=altcode:n</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_noaltcode" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=noaltcode\b">
<![CDATA[
 <p>Always execute the parallelized version of a loop regardless of the loop count.</p>
]]>
<example>-Mconcur=noaltcode</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_noassoc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=noassoc\b" >
<![CDATA[
 <p>Disables parallelization of loops with reductions.</p>
]]>
<example>-Mconcur=noassoc</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_cncall" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=cncall\b">
<![CDATA[
 <p>Assume loops containing calls are safe to parallelize and allows loops containing calls to be
 candidates for parallelization.  Also, no minimum loop count threshold must be satisfied before
 parallelization will occur, and last values of scalars are assumed to be safe.</p>
]]>
<example>-Mconcur=cncall</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_nocncall" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=nocncall\b">
<![CDATA[
 <p>Do not assume loops containing calls are safe to parallelize.</p>
]]>
<example>-Mconcur=nocncall</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_dist_block" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=dist:block\b">
<![CDATA[
 <p>Parallelize with block distribution.  Contiguous blocks of iterations of a parallelizable loop
 are assigned to the available processors.</p>
]]>
<example>-Mconcur=dist:bloc</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_dist_cyclic" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=dist:cyclic\b">
<![CDATA[
 <p>Parallelize with cyclic distribution.  The outermost parallelizable loop in any loop nest is
 parallelized.  If a parallelized loop is innermost, its iterations are allocated to processors cyclically.
 For example, if there are 3 processors executing a loop, processor 0 performs iterations 0, 3, 6, etc.; processor 1
 performs iterations 1, 4, 7, etc.; and processor 2 performs iterations 2, 5, 8, etc.</p>
]]>
<example>-Mconcur=dist:cyclic</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_innermost" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=innermost\b">
<![CDATA[
 <p>Enable parallelization of innermost loops.</p>
]]>
<example>-Mconcur=innermost</example>
<include flag="Mconcur" />
</flag>

<flag name="Mconcur_noinnermost" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur=noinnermost\b">
<![CDATA[
 <p>Disable parallelization of innermost loops.</p>
]]>
<example>-Mconcur=noinnermost</example>
<include flag="Mconcur" />
</flag>


<flag name="Mconcur" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mconcur\b">
<![CDATA[
  <p>Instructs the compiler to enable auto-concurrentization of loops.
  If <i>-Mconcur</i> is specified, multiple processors will be used
  to execute loops that the compiler determines to be parallelizable.</p>
  <p>The environment variables MP_BIND, MP_LIST, and OMP_NUM_THREADS
  may be used to optimise the runtime behavior of binaries
  compiled with <i>-Mconcur</i>.
  These variables are described below in the section "System and other
  Tuning Information".</p>
]]>
<example>-Mconcur</example>
</flag>

<flag name="Minline_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=([^,\s]+),(\S+)\b">
<include text="-Minline=$1" />
<include text="-Minline=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Minline_lib" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=lib:([\.\-\w]+)\b">
<![CDATA[
 <p>Instructs the inliner to inline the functions within the library <b>filename.ext</b>.</p>
]]>
<example>-Minline=lib:filename.ext</example>
</flag>

<flag name="Minline_except" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=except:([\-\w,]+)\b" >
<![CDATA[
 <p>Instructs the inliner to inline all eligible functions except <b>$1</b>, a function in the source text.
 Multiple functions can be listed, comma-separated.</p>
]]>
<example>-Minline=except:func</example>
</flag>

<flag name="Minline_name" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=name:([\-\w,]+)\b" >
<![CDATA[
 <p>Instructs the inliner to inline function <b>func</b>.</p>
]]>
<example>-Minline=name:func</example>
</flag>

<flag name="Minline_reshape" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=reshape\b">
<![CDATA[
 <p>Allows inlining in Fortran even when array shapes do not match.</p>
]]>
<example>-Minline=reshape</example>
</flag>

<flag name="Minline_size" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=size:(\d+)\b">
<![CDATA[
 <p>Instructs the inliner to inline functions with <b>$1</b> or fewer statements where <b>$1</b> is a supplied constant value.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Minline=size:n</example>
</flag>

<flag name="Minline_levels" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline=levels:(\d+)\b">
<![CDATA[
 <p>Instructs the inliner to perform <b>$1</b> levels of inlining where <b>$1</b> is a supplied constant value.  If no value is suppiled, then the default value of 2 is used.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Minline=levels:4</example>
</flag>

<flag name="Minline" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Minline\b">
<![CDATA[
 <p>Instructs the inliner to perform 1 level of inlining.</p>
]]>
<example>-Minline</example>
</flag>

<flag name="Mnopropcond" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnopropcond\b">
<![CDATA[
 <p>Disable constant propagation from assertions derived from equality conditionals.</p>
]]>
<example>-Mnopropcond</example>
</flag>

<flag name="Msmartalloc_huge_n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msmartalloc\=huge\:(\d+)\b">
<![CDATA[
  <p>Link with the huge page runtime library and allocate a maximum of
  <b>$1</b> huge pages where <b>$1</b> is a supplied constant value.
  If no constant value is supplied, then the maximum number of huge
  pages the application can use is limited by the number of huge
  pages the operating system has available or the value
  of the environment variable PGI_HUGE_PAGES.</p>
  <p>Note that setting PGI_HUGE_PAGES will override the value of <b>$1</b>.
  This environment variable is described below in the section
  "System and Other Tuning Information". </p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Msmartalloc=huge:150</example>
</flag>

<flag name="Msmartalloc_huge" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msmartalloc\=huge\b">
<![CDATA[
  <p>Link with the huge page runtime library.
  The maximum number of huge pages the application can use is limited
  by the number of huge pages the operating system has available
  or the value of the environment variable PGI_HUGE_PAGES.
  This environment variable is described below in the section
  "System and Other Tuning Information". </p>
]]>
<example>-Msmartalloc=huge</example>
</flag>

<flag name="Msmartalloc_hugebss" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msmartalloc\=hugebss\b">
<![CDATA[
 <p>Link with the huge page runtime library.  Use huge pages for an executable's .BSS section.</p>
]]>
<example>-Msmartalloc\=hugebss</example>
</flag>

<flag name="Msmartalloc_lin" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msmartalloc\b">
<![CDATA[
 <p>Adds a call to the routine "mallopt" in the main routine.  This option can have a dramatic impact on the performance of programs that dynamically allocate memory, especially for those which have a few large mallocs.  To be effective, this switch must be specified when compiling the file containing the Fortran, C, or C++ main routine.</p>
]]>
<example>-Msmartalloc</example>
</flag>

<flag name="Msafeptr_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msafeptr=([^,\s]+),(\S+)\b">
<include text="-Msafeptr=$1" />
<include text="-Msafeptr=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Msafeptr_all" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=all\b">
<![CDATA[
 <p>Assume all pointers and arrays are independent and safe for aggressive optimizations,
 and in particular that no pointers or arrays overlap of conflict with each other.</p>
]]>
<example>-Msafeptr=all</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr_arg" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=arg\b">
<![CDATA[
 <p>Instructs the compiler that arrays and pointers are treated with the same copyin and copyout
 semantics as Fortran dummy arguments.</p>
]]>
<example>-Msafeptr=arg</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr_auto" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=auto\b">
<![CDATA[
 <p>Instructs the compiler that local pointers and arrays do not overlap or
 conflict with each other and are independent.</p>
]]>
<example>-Msafeptr=auto</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr_local" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=local\b">
<![CDATA[
 <p>Instructs the compiler that local pointers and arrays do not overlap or
 conflict with each other and are independent.</p>
]]>
<example>-Msafeptr=local</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr_static" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=static\b">
<![CDATA[
 <p>Instructs the compiler that static pointers and arrays do not overlap or conflict
 with each other and are independent.</p>
]]>
<example>-Msafeptr=static</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr_global" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr=global\b">
<![CDATA[
 <p>Instructs the compiler that global or external pointers and arrays do not overlap or
 conflict with each other and are independent.</p>
]]>
<example>-Msafeptr=global</example>
<include flag="Msafeptr" />
</flag>

<flag name="Msafeptr" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="-Msafeptr\b">
<![CDATA[
 <p>Instructs the C/C++ compiler to override data dependencies between pointers of a given storage class.</p>
]]>
<example>-Msafeptr</example>
</flag>

<flag name="Munroll_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll=([^,\s]+),(\S+)\b">
<include text="-Munroll=$1" />
<include text="-Munroll=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Munroll_c_n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll=c:(\d+)\b">
<![CDATA[
 <p>Instructs the compiler to completely unroll loops with a constant loop count of less than
 or equal to <b>$1</b> where <b>$1</b> is a supplied constant value.  If no constant value is given, then a default of 4 is used.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Munroll=c:1</example>
<include flag="Munroll" />
</flag>

<flag name="Munroll_n_n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll=n:(\d+)\b">
<![CDATA[
 <p>"-Munroll=n:n" instructs the compiler to unroll loops <b>$1</b> times where <b>$1</b> is a supplied constant value.
If no constant value is given, then a default of 4 is used.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Munroll=n:n</example>
<include flag="Munroll" />
</flag>

<flag name="Munroll_m_n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll=m:(\d+)\b">
<![CDATA[
 <p>"-Munroll=m:n" instructs the compiler to unroll loops with multiple blocks <b>$1</b> times where <b>$1</b> is a supplied constant value.
If no constant value is given, then a default of 4 is used.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Munroll=m:n</example>
<include flag="Munroll" />
</flag>

<flag name="Munroll_m" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll=m\b">
<![CDATA[
 <p>Instructs the compiler to unroll loops with multiple blocks using the default value of 4 times</p>
]]>
<example>-Munroll=m</example>
<include flag="Munroll" />
</flag>

<flag name="Munroll" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Munroll\b">
<![CDATA[
 <p>Invokes the loop unroller.</p>
]]>
<example>-Munroll</example>
</flag>

<flag name="Mnounroll" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnounroll\b">
<![CDATA[
 <p>Disable loop unrolling.</p>
]]>
<example>-Mnounroll</example>
</flag>

<flag name="Mnodepchk" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="\-Mnodepchk\b">
<![CDATA[
 <p>Don't check dependence relations for vector or parallel code.</p>
]]>
</flag>

<flag name="Msafe_lastval" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="\-Msafe_lastval\b">
<![CDATA[
 <p>Allow parallelization of loops with conditional scalar assignments.</p>
]]>
</flag>

<flag name="Mstride0" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="\-Mstride0\b">
<![CDATA[
 <p>Generate code to check for zero loop increments.</p>
]]>
</flag>

<flag name="Msmart" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Msmart\b">
<![CDATA[
 <p>Enable an optional post-pass instruction scheduling.</p>
]]>
<example>-Msmart</example>
</flag>

<flag name="Mnosmart" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnosmart\b">
<![CDATA[
 <p>Disable an optional post-pass instruction scheduling.</p>
]]>
<example>-Mnosmart</example>
</flag>

<flag name="Mvect_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=([^,\s]+),([\:\S]+)\b">
<include text="-Mvect=$1" />
<include text="-Mvect=$2" />
<display enable="0" />
CPU2006 flags file rule used to split an optimization flag containing sub-options into multiple flag descriptions.
Please refer to the flag file rule of the various sub-options for the actual flag description.
</flag>

<flag name="Mnovect" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnovect\b">
<![CDATA[
 <p>Disable automatic vector pipelining.</p>
]]>
<example>-Mnovect</example>
</flag>

<flag name="Mvect_altcode" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=altcode\b">
<![CDATA[
 <p>Instructs the vectorizer to generate alternate code for vectorized loops when appropriate.  For each
 vectorized loop the compiler decides whether to generate altcode and what type or types to generate, which may
 be any or all of:</p>
<ul>
<li>Altcode without iteration peeling</li>
<li>Altcode with non-temporal stores and other data cache optimizations</li>
<li>Altcode base on array alignments calculated dynamically at runtime.</li>
</ul>
<p>The compiler also determines suitable loop count and array alignment conditions for executing the altcode.</p>
]]>
<example>-Mvect=altcode</example>
</flag>

<flag name="Mvect_noaltcode" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=noaltcode\b">
<![CDATA[
 <p>Disables alternate code generation for vectorized loops.</p>
]]>
<example>-Mvect=noaltcode</example>
</flag>

<flag name="Mvect_assoc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=altcode\b">
<![CDATA[
 <p>Instructs the vectorizer to enable certain associativity conversions that can change the results of a computations
 due to roundoff error.  A typical optimization is to change an arithmetic operation to an arithmetic opteration that is
 mathmatically correct, but can be computationally different, due to round-off error.</p>
]]>
<example>-Mvect=assoc</example>
</flag>

<flag name="Mvect_noassoc" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=noassoc\b">
<![CDATA[
 <p>Instructs the vectorizer to disable associativity conversions.</p>
]]>
<example>-Mvect=noassoc</example>
</flag>

<flag name="Mvect_cachesize_n" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="\-Mvect=cachesize:(\d+)\b">
<![CDATA[
 <p>Instructs the vectorizer, when performing cache tiling optimizations, to assume a cache size of <b>$1</b>.
 The default size is processor dependent.</p>
]]>
<ex_replacement>n</ex_replacement>
<example>-Mvect=cachesize:n</example>
</flag>

<flag name="Mvect_fuse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=fuse\b">
<![CDATA[
 <p>Instructs the vectorizer to enable loop fusion.</p>
]]>
<example>-Mvect=fuse</example>
<include flag="Mvect" />
</flag>

<flag name="Mvect_nogather" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=nogather\b">
<![CDATA[
 <p>Instructs the vectorizer to disable vectorization of indirect array references.</p>
]]>
<example>-Mvect=nogather</example>
<include flag="Mvect" />
</flag>

<flag name="Mvect_idiom" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=idiom\b">
<![CDATA[
 <p>Instructs the vectorizer to enable idiom recognition.</p>
]]>
<example>-Mvect=idiom</example>
</flag>

<flag name="Mvect_noidiom" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=noidiom\b">
<![CDATA[
 <p>Instructs the vectorizer to disable idiom recognition.</p>
]]>
<example>-Mvect=noidiom</example>
</flag>

<flag name="Mvect_nosizelimit" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=nosizelimit\b">
<![CDATA[
 <p>Generate vector loops for all loops where possible regardless of the number of
 statements in the loop.  This overrides a heuristic in the vectorizer that ordinarily
 prevents vectorization of loops with a number of statements that exceed a certain threshold.</p>
]]>
<example>-Mvect=nosizelimit</example>
<include flag="Mvect" />
</flag>

<flag name="Mvect_partial" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=partial\b">
<![CDATA[
 <p>Instructs the vectorizer to generate partial vectorization.</p>
]]>
<example>-Mvect=partial</example>
<include flag="Mvect" />
</flag>

<flag name="Mvect_prefetch" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=prefetch\b">
<![CDATA[
 <p>Instructs the vectorizer to generate prefetch instructions.</p>
]]>
<example>-Mvect=prefetch</example>
<include flag="Mvect" />
</flag>

<flag name="Mvect_sse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=sse\b">
<![CDATA[
 <p>Instructs the vectorizer to search for vectorizable loops and, where possible, make use of
 SSE, SSE2, and prefetch instructions.</p>
]]>
<include flag="Mvect" />
<example>-Mvect=sse</example>
</flag>

<flag name="Mvect_nosse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect=nosse\b">
<![CDATA[
 <p>Instructs the driver to disable the -Mvect=sse option which is part of the "-fast" option.</p>
]]>
<include flag="Mvect_sse" />
<include flag="fast" />
<example>-Mvect=nosse</example>
</flag>

<flag name="Mvect" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mvect\b">
<![CDATA[
 <p>Enable automatic vector pipelining.</p>
]]>
<include flag="Mvect_assoc" />
<include flag="Mvect_altcode" />
<include text="Mvect=cachesize:262144" />
<example>-Mvect</example>
</flag>

<flag name="Mnofptrap" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mnofptrap\b">
<![CDATA[
 <p>Disables -Ktrap=fp.</p>
]]>
<example>-Mnofptrap</example>
<include flag="Ktrap" />
</flag>

<flag name="Ktrap" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Ktrap\w*\b">
<![CDATA[
 <p>-Ktrap is only processed by the compilers when compiling main functions' programs. The options inv, denorm, divz, ovf, unf, and inexact correspond to the processor's exception mask bits invalid operation, denormalized operand, divide-by-zero, overflow, underflow, and precision, respectively. Normally, the processor's exception mask bits are on (floating-point exceptions are masked the processor recovers from the exceptions and continues). If a floating-point exception occurs and its corresponding mask bit is off (or  unmasked ), execution terminates with an arithmetic exception (C's SIGFPE signal). -Ktrap=fp is equivalent to -Ktrap=inv,divz,ovf.
</p>
]]>
<example>-Ktrap=fp</example>
</flag>

<flag name="Mlongbranch" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlongbranch\b">
<![CDATA[
 <p>Enable long branches.</p>
]]>
<example>-Mlongbranch</example>
</flag>

<flag name="acml" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-lacml\b">
<![CDATA[
 <p>Link with the AMD Core Math Library. Available from www.amd.com</p>
]]>
<example>-lacml</example>
</flag>

<flag name="mp" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-mp\b">
<![CDATA[
  <p>Use the -mp option to instruct the compiler to interpret
  user-inserted OpenMP shared-memory parallel programming directives
  and generate an executable file which will utilize multiple
  processors in a shared-memory parallel system.</p>
  <p>When used strictly as a linker flag, the PGI OpenMP runtime
  will be linked and users can use the environment variables MP_BIND
  and MP_BLIST to bind a serial program to a CPU.</p>
  <p>The environment variables MP_BIND, MP_LIST, and OMP_NUM_THREADS
  may be used to optimise the runtime behavior of binaries
  compiled with <i>-mp</i>.
  These variables are described below in the section "System and other
  Tuning Information".</p>
]]>
<example>-mp</example>
</flag>

<flag name="mp_align" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-mp=align\b">
<![CDATA[
 <p>The align sub-option to -mp forces loop iterations to be allocated to OpenMP processes using an algorithm that maximizes alignment of vector sub-sections in loops that are both parallelized and vectorized for SSE. This can improve performance in program units that include many such loops. It can result in load-balancing problems that significantly decrease performance in program units with relatively short loops that contain a large amount of work in each iteration. </p>
]]>
<example>-mp=align</example>
<include flag="mp" />
</flag>

<flag name="mp_numa" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-mp=numa\b">
<![CDATA[
 <p>The numa suboption to -mp uses libnuma on systems where it is available.</p>
]]>
<example>-mp=numa</example>
<include flag="mp" />
</flag>

<flag name="mp_nonuma" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-mp=nonuma\b">
<![CDATA[
 <p>The nonuma suboption to -mp tells the driver to not link with libnuma.</p>
]]>
<example>-mp=nonuma</example>
<include flag="mp" />
</flag>

<flag name="mcmodel_medium" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-mcmodel=medium\b">
<![CDATA[
 <p>(For use only on 64-bit Linux targets) Generate code for the medium memory model in the linux86-64 execution environment. The default small memory model of the linux86-64 environment limits the combined area for a user's object or executable to 1GB, with the Linux kernel managing usage of the second 1GB of address for system routines, shared libraries, stacks, etc. Programs are started at a fixed address, and the program can use a single instruction to make most memory references. The medium memory model allows for larger than 2GB data areas, or .bss sections. Program units compiled using either -mcmodel=medium or -fpic require additional instructions to reference memory. The effect on performance is a function of the data-use of the application. The -mcmodel=medium switch must be used at both compile time and link time to create 64-bit executables. Program units compiled for the default small memory model can be linked into medium memory model executables as long as they are compiled -fpic, or position-independent.</p>
]]>
<example>-mcmodel=medium</example>
<include flag="Mlarge_arrays" />
</flag>


<flag name="Mlarge_arrays" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mlarge_arrays\b">
<![CDATA[<p>Enable support for 64-bit indexing and single static data objects larger than 2GB in size. This option is default in the presence of -mcmodel=medium. Can be used separately together with the default small memory model for certain 64-bit applications that manage their own memory space.</p>
]]>
<example>-Mlarge_arrays</example>
</flag>

<flag name="Mdse" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mdse\b">
<![CDATA[
<p>Enable dead store elimination.</p>
]]>
</flag>

<flag name="alias_ansi" class="optimization"
 compilers="C_PGI, Cplusplus_PGI"
 regexp="\-alias\=ansi\b">
<![CDATA[
<p>Enable optimizations using ANSI C type-based pointer disambiguation.</p>
]]>
</flag>


<flag name="Odefault" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O\b">
<![CDATA[
 <p>Set the optimization level to -O2</p>
]]>
<include flag="O2" />
<example>-O</example>
</flag>

<flag name="O0" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O0\b">
<![CDATA[
 <p>A basic block is generated for each C statement.  No scheduling is done
between statements.  No global optimizations are performed.</p>
]]>
<example>-O0</example>
</flag>

<flag name="O1" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O1\b">
<![CDATA[
 <p>Level-one optimization specifies local optimization (-O1). The compiler performs scheduling of basic blocks as well as register allocation. This optimization level is a good choice when the code is very irregular; that is it contains many short statements containing IF statements and the program does not contain loops (DO or DO WHILE statements). For certain types of code, this optimization level may perform better than level-two (-O2) although this case rarely occurs.</p>
<p>The PGI compilers perform many different types of local optimizations, including but not limited to:</p>
<ul>
<li>Algebraic identity removal</li>
<li>Constant folding</li>
<li>Common subexpression elimination</li>
<li>Local register optimization</li>
<li>Peephole optimizations</li>
<li>Redundant load and store elimination</li>
<li>Strength reductions</li>
</ul>

]]>
<example>-O1</example>
</flag>

<flag name="O2" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O2\b">
<![CDATA[
 <p>
Level-two optimization (-O2 or -O) specifies global optimization. The -fast option generally will specify global optimization; however, the -fast switch will vary from release to release depending on a reasonable selection of switches for any one particular release. The -O or -O2 level performs all level-one local optimizations as well as global optimizations. Control flow analysis is applied and global registers are allocated for all functions and subroutines. Loop regions are given special consideration. This optimization level is a good choice when the program contains loops, the loops are short, and the structure of the code is regular.</p>
<p>The PGI compilers perform many different types of global optimizations, including but not limited to:</p>
<ul>
<li>Branch to branch elimination</li>
<li>Constant propagation</li>
<li>Copy propagation</li>
<li>Dead store elimination</li>
<li>Global register allocation</li>
<li>Invariant code motion</li>
<li>Induction variable elimination</li>
</ul>
</p>
]]>
<include flag="O1" />
<example>-O2</example>
</flag>

<flag name="O3" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O3\b">
<![CDATA[
 <p>All level 1 and 2 optimizations are performed.
In addition, this level enables more aggressive code hoisting and scalar replacement optimizations that may or may not be profitable.</p>
]]>
<include flag="O2" />
<example>-O3</example>
</flag>

<flag name="O4" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-O4\b">
<![CDATA[
 <p>Performs all level 1, 2, and 3 optimizations and enables hoisting of guarded invariant floating point expressions.</p>
]]>
<include flag="O3" />
<example>-O4</example>
</flag>

<flag name="tp_subopt" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+([^,\s]+),(\S+)\b">
<include text="-tp $1" />
<include text="-tp $2" />
<display enable="1" />
Create a Unified Binary using multiple targets.
</flag>

<flag name="tpk8-32" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+k8-32\b">
<![CDATA[
 <p>Specify the type of the target processor as AMD64 Processor 32-bit mode.</p>
]]>
<example>-tp k8-32</example>
</flag>

<flag name="tpk8-64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+k8-64\b">
<![CDATA[
 <p>Specify the type of the target processor as AMD64 Processor 64-bit mode.</p>
]]>
<example>-tp k8-64</example>
</flag>

<flag name="tpbarcelona-64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+barcelona-64\b">
<![CDATA[
 <p>Specify the type of the target processor as AMD64 Barcelona Processor 64-bit mode.</p>
]]>
<example>-tp barcelona-64</example>
</flag>


<flag name="tpbarcelona32" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+barcelona-32\b">
<![CDATA[
 <p>Specify the type of the target processor as AMD64 Barcelona Processor 32-bit mode.</p>
]]>
<example>-tp barcelona-32</example>
</flag>


<flag name="tpbarcelona" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+barcelona\b">
<![CDATA[
 <p>Specify the type of the target processor as AMD64 Barcelona Processor 32-bit mode.</p>
]]>
<example>-tp barcelona</example>
</flag>


<flag name="tppenryn-64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+penryn-64\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel Penryn Processor 64-bit mode.</p>
]]>
<example>-tp penryn-64</example>
</flag>


<flag name="tppenryn32" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+penryn-32\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel Penryn Processor 32-bit mode.</p>
]]>
<example>-tp penryn-32</example>
</flag>


<flag name="tppenryn" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+penryn\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel Penryn Processor 32-bit mode.</p>
]]>
<example>-tp penryn</example>
</flag>


<flag name="tpp7-64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+p7-64\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel P7 Architecture with
 EM64t, 64-bit mode.</p>
]]>
<example>-tp p7-64</example>
</flag>

<flag name="tpp7" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+p7\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel P7 Architecture (Pentium
 4, Xeon, Centrino).</p>
]]>
<example>-tp p7</example>
</flag>

<flag name="tpcore2-64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+core2-64\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel Core 2 EM64T or compatible architecture using 64-bit mode.</p>
]]>
<example>-tp core2-64</example>
</flag>

<flag name="tpcore2" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+core2\b">
<![CDATA[
 <p>Specify the type of the target processor as Intel Core 2 or compatible architecture using 32-bit mode.</p>
]]>
<example>-tp core2</example>
</flag>

<flag name="tpx64" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+x64\b">
<![CDATA[
 <p>Use the unified AMD/Intel 64-bit mode.</p>
]]>
<example>-tp x64</example>
</flag>


<flag name="tp" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-tp\s+([\-\w]+)\b">
<include text="-tp $1" />
<display enable="0" />
</flag>


<flag name="Mx" class="optimization"
 compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
 regexp="-Mx[\,x\d]+\b">
<![CDATA[
<p>Experimental flags.</p>
]]>
</flag>

   <flag name="F-fb_create_fbdata" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-fb_create fbdata">
      <example>-fb_create fbdata</example>
      <![CDATA[
         <p>-fb_create &lt;path&gt;<br>
         Used to specify that an instrumented executable program is to be
         generated. Such an executable is suitable for producing feedback
         data files with the specified prefix for use in feedback-directed
         optimization (FDO).
         The commonly used prefix is "fbdata".<br>
         This is OFF by default.</p>
         <p>During the training run, the instrumented executable produces information
         regarding execution paths and data values, but
         does not generate information by using hardware performance counters. </p>
      ]]>
   </flag>

   <flag name="F-fb_opt_fbdata" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-fb_opt fbdata">
      <example>-fb_opt fbdata</example>
      <![CDATA[
         <p>-fb_opt &lt;prefix for feedback data files&gt;<br>
         Used to specify feedback-directed optimization (FDO) by extracting
         feedback data from files with the specified prefix, which were
         previously generated using -fb-create.
         The commonly used prefix is "fbdata".
         The same optimization flags should be used
         for both the -fb-create and fb_opt compile steps.
         Feedback data files created from executables compiled
         with different optimization flags may give checksum errors.<br>
         FDO is OFF by default.</p>
         <p>During the -fb_opt compilation phase, information regarding execution paths
         and data values are used to improve the information available to the optimizer.
         FDO enables some optimizations which are only performed when the feedback data file
         is available. The safety of optimizations performed under FDO is consistent
         with the level of safety implied by the other optimization flags
         (outside of fb_create and fb_opt) specified on the compile and link lines.</p>
      ]]>
   </flag>

   <flag name="F-march" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-march=(barcelona|opteron|athlon64|athlon64fx|core|em64t|pentium4|xeon|anyx86|auto)">
      <![CDATA[
         <p>-march=&lt;cpu-type&gt;
         </p>
         <p>Compiler will optimize code for selected cpu-type:
         opteron, athlon, athlon64, athlon64fx, barcelona, em64t,
         pentium4, xeon, core, anyx86, auto.<br>
         The default value, <b>auto</b>, means to optimize for the platform
         on which the compiler is running,
         as determined by reading /proc/cpuinfo.<br>
         <b>anyx86</b> means a generic 32-bit x86 processor
         without SSE2 support.<br>
         <b>barcelona</b> is AMD's first Quad-core processor family.
         </p>
      ]]>
   </flag>

   <flag name="F-O_n" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-O[0-3]\b">
      <example>-O3</example>
      <![CDATA[
         <p>Specify the basic level of optimization desired.<br>
         The options can be one of the following:</p>

            <p style="text-indent: -25px; margin-left: 25px">
               0&nbsp;&nbsp;&nbsp; Turn off all optimizations.</p>

            <p style="text-indent: -25px; margin-left: 25px">
               1&nbsp;&nbsp;&nbsp; Turn on local optimizations that
               can be done quickly. Do peephole optimizations and
               instruction scheduling.</p>

            <p style="text-indent: -25px; margin-left: 25px">
               2&nbsp;&nbsp;&nbsp; Turn on extensive optimization.
               This is the default.<br>
               The optimizations at this level are generally conservative,
               in the sense that they are virtually always beneficial and
               avoid changes which affect
               such things as floating point accuracy.  In addition to the level
               1 optimizations, do inner loop
               unrolling, if-conversion, two passes of instruction scheduling,
               global register allocation, dead store elimination,
               instruction scheduling across basic blocks,
               and partial redundancy elimination.</p>

            <p style="text-indent: -25px; margin-left: 25px">
               3&nbsp;&nbsp;&nbsp; Turn on aggressive optimization.<br>
               The optimizations at this level are distinguished from -O2
               by their aggressiveness, generally seeking highest-quality
               generated code even if it requires extensive compile time.
               They may include optimizations that are generally beneficial
               but may hurt performance.<br>
               This includes but is not limited to turning on the
               Loop Nest Optimizer, -LNO:opt=1, and setting
               -OPT:roundoff=1:IEEE_arithmetic=2:Olimit=9000:reorg_common=ON.</p>

            <p style="text-indent: -25px; margin-left: 25px">
               s&nbsp;&nbsp;&nbsp; Specify that code size is to be given
               priority in tradeoffs with execution time.</p>

         If no value is specified, 2 is assumed.</p>
      ]]>
   </flag>

   <flag name="F-Ofast" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-Ofast">
      <example>-Ofast</example>
      <![CDATA[
         <p>Equivalent to -O3 -ipa -OPT:Ofast -fno-math-errno -ffast-math.<br>
         Use optimizations selected to maximize performance.
         Although the optimizations are generally safe, they may affect
         floating point accuracy due to rearrangement of computations.</p>
         <p>NOTE: -Ofast enables -ipa (inter-procedural analysis),
         which places limitations on how libraries and .o files are built.</p>
      ]]>
      <include flag="F-O_n" />
      <include flag="F-ipa" />
      <include flag="F-OPT:Ofast" />
      <include flag="F-fno-math-errno" />
      <include flag="F-ffast-math" />
      <display enable="1" />
   </flag>

   <flag name="F-apo" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-apo">
      <example>-apo</example>
      <![CDATA[
         <p>This auto-parallelizing option signals the compiler
         to automatically convert sequential code into parallel code
         where it is safe and beneficial to do so.
         </p>
         <p>The default number of threads used at run-time
         is the number of CPUs available in the machine.
         This number of threads can also be controlled by setting
         the OMP_NUM_THREADS environment variable.
         </p>
      ]]>
   </flag>

   <flag name="F-ipa" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-ipa">
      <example>-ipa</example>
      <![CDATA[
         <p>Invoke inter-procedural analysis (IPA). Specifying this option is
         identical to specifying -IPA or -IPA:.
         Default settings for the individual IPA suboptions are used.</p>
      ]]>
   </flag>

   <flag name="F-m3dnow" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-m3dnow">
      <example>-m3dnow</example>
      <![CDATA[
         <p>Enable the use of 3DNow instructions.</p>
      ]]>
   </flag>

   <flag name="F-ffast-math" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-f(no-|)fast-math">
      <example>-ffast-math</example>
      <![CDATA[
         <p>-ffast-math improves FP speed by relaxing ANSI & IEEE rules.
         -fno-fast-math tells the compiler to conform to ANSI and IEEE
         math rules at the expense of speed. -ffast- math implies
         -OPT:IEEE_arithmetic=2 -fno-math-errno.   -fno-fast-math
         implies -OPT:IEEE_arithmetic=1 -fmath-errno.</p>
      ]]>
   </flag>

   <flag name="F-fexceptions" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-f(no-|)exceptions">
      <example>-fno-exceptions</example>
      <![CDATA[
         <p>(For C++ only) -fexceptions enables exception handling.
         This is the default.
         -fno-exceptions disables exception handling.</p>
      ]]>
   </flag>

   <flag name="F-fno-math-errno" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale">
      <example>-fno-math-errno</example>
      <![CDATA[
         <p>Do not set ERRNO after calling math functions that are executed
         with a single instruction, e.g. sqrt. A program that relies on IEEE
         exceptions for math error handling may want to use this flag for speed
         while maintaining IEEE arithmetic compatibility. This is implied by
         -Ofast. The default is -fmath-errno.</p>
      ]]>
   </flag>

   <flag name="F-m32" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-m32">
      <example>-m32</example>
      <![CDATA[
         <p>Compile for 32-bit ABI, also known as x86 or IA32.</p>
      ]]>
   </flag>

   <flag name="F-m64" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-m64">
      <example>-m64</example>
      <![CDATA[
         <p>Compile for 64-bit ABI, also known as AMD64, x86_64, or IA32e.  On a
        32-bit host, the default is 32-bit ABI.  On a 64-bit host, the default
        is  64-bit ABI if the target platform (-march/-mcpu/-mtune) is 64-bit;
        otherwise the default is 32-bit.</p>
      ]]>
   </flag>

   <!-- Splitter for the flag groups      -->
   <!-- -CG:, -IPA:, -LNO:, -OPT:, -WOPT: -->

   <flag name="F-splitting:all" class="optimization"
         regexp="-(CG|IPA|LNO|OPT|WOPT|GRA|LANG|TENV):([^:\s]+):(\S+)(?=\s|$)">
      <include text="-$1:$2" />
      <include text="-$1:$3" />
      <display enable="0" />
    This rule is used to split a flag group containing sub-options into multiple flag descriptions.
    Please refer to the flag file rule of the various sub-options for the actual flag description.
   </flag>

   <!-- Sub-flags of the -CG: group -->

   <flag name="F-CG:cflow" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:cflow=(on|off|0|1)">
      <example>-CG:cflow</example>
      <![CDATA[
         <p>The Code Generation option group -CG: controls the optimizations
         and transformations of the instruction-level code generator.</p>

         <p>-CG:flow : OFF disables control flow optimization in the code
         generation. Default is ON.</p>
      ]]>
   </flag>

  <flag name="F-CG:cse_regs" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:cse_regs=\d+">
      <example>-CG:cse_regs</example>
      <![CDATA[
         <p>-CG:cse_regs=N :  When performing common subexpression elimination during code generation,
         assume there are N extra integer registers available over the number provided by the CPU. N can
         be positive, zero, or negative.  The  default is positive infinity.  See also -CG:sse_cse_regs.</p>
      ]]>
   </flag>

   <flag name="F-CG:gcm" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:gcm=(on|off|0|1)">
      <example>-CG:gcm</example>
      <![CDATA[
         <p>-CG:gcm : Specifying OFF disables the instruction-level
         global code motion optimization phase. The default is ON.</p>
      ]]>
   </flag>

   <flag name="F-CG:load_exe" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:load_exe=\d+">
      <example>-CG:load_exe</example>
      <![CDATA[
         <p>-CG:load_exe=N : Specify the threshold for subsuming a memory load
         operation into the operand of an arithmetic instruction.
         The value of 0 turns off this subsumption optimization.
         If N is 1, this subsumption is performed only when the result of
         the load has only one use.
         This subsumption is not performed if the number of times the result
         of the load is used exceeds the value N, a non-negative integer.<br>
         If the ABI is 64-bit and the language is Fortran, the default for N
         is 2, otherwise the default is 1.</p>
      ]]>
   </flag>

   <flag name="F-CG:local_fwd_sched" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:local_fwd_sched=(on|off|0|1)">
      <example>-CG:local_fwd_sched</example>
      <![CDATA[
         <p>-CG:local_fwd_sched : this optimization option is deprecated.</p>
      ]]>
   </flag>

   <flag name="F-CG:local_sched_alg" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:local_sched_alg=(0|1|2)">
      <example>-CG:local_sched_alg</example>
      <![CDATA[
         <p>-CG:local_sched_alg : Select the basic block instruction scheduling algorithm.
          If 0, perform backward scheduling, where instructions are scheduled from the
          bottom of the basic block to the top.  If 1, perform forward scheduling. If 2,
          schedule  the  instructions  twice  - once in the forward direction and once in
          the backward direction - and take the better of the two schedules.  The default
          value of this option is determined by the compiler during compilation.</p>
      ]]>
   </flag>

   <flag name="F-CG:locs_shallow_depth" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:locs_shallow_depth=(on|off|0|1)">
      <example>-CG:locs_shallow_depth</example>
      <![CDATA[
         <p>-CG:locs_shallow_depth=(ON|OFF): When performing local instruction scheduling to reduce
                register usage, give priority to instructions that have shallow depths in the
                dependence graph. The default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-CG:movnti" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:movnti=\d+">
      <example>-CG:movnti</example>
      <![CDATA[
         <p>-CG:movnti=N : Convert ordinary stores to non-temporal stores
         when writing memory blocks of size larger than  N KB.  When  N
         is set to 0, this transformation is avoided.
         The default value is 1000 (KB).</p>
      ]]>
   </flag>

   <flag name="F-CG:p2align" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:p2align=(on|off|0|1)">
      <example>-CG:p2align</example>
      <![CDATA[
         <p>-CG:p2align : Align loop heads to 64-byte boundaries. The default is off.</p>
      ]]>
   </flag>

   <flag name="F-CG:post_local_sched" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:post_local_sched=(on|off|0|1)">
      <example>-CG:post_local_sched</example>
      <![CDATA[
         <p>-CG:post_local_sched: Enable the local scheduler phase after register allocation.
         The default is on.</p>
      ]]>
   </flag>

   <flag name="F-CG:prefetch" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:prefetch=(on|off|0|1)">
      <example>-CG:prefetch</example>
      <![CDATA[
         <p>-CG:prefetch : Enable or disable generation of prefetch instructions in the code
         generator.  The default is on.</p>
      ]]>
   </flag>

   <flag name="F-CG:prefer_legacy_regs" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:prefer_legacy_regs=(on|off|0|1)">
      <example>-CG:prefer_legacy_regs</example>
      <![CDATA[
         <p>-CG:prefer_legacy_regs: Tell the local register allocator to use the first 8 integer
          and SSE registers whenever possible (%rax-%rbp,%xmm0-%xmm7).  Instructions using these
          registers have smaller instruction sizes.  The default is OFF</p>
      ]]>
   </flag>

   <flag name="F-CG:ptr_load_use" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:ptr_load_use=\d+">
      <example>-CG:ptr_load_use</example>
      <![CDATA[
         <p>-CG:ptr_load_use=N: Add a latency of N cycles between an instruction that loads a pointer
         and an instruction that uses the pointer. The extra latency will force the instruction scheduler
         to schedule the pointer load earlier. In general, it is beneficial to load pointers as soon as
         possible so that dependent memory instructions can begin execution.  N is 4 by default.
         ("Load pointer" instructions include load-execute instructions that compute a pointer result.)</p>
      ]]>
   </flag>

   <flag name="F-CG:push_pop_int_saved_regs" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:push_pop_int_saved_regs=(on|off|1|0)">
      <example>-CG:push_pop_int_saved_regs</example>
      <![CDATA[
         <p>-CG:push_pop_int_saved_regs: Use the X86 push and pop instructions to save the integer
         callee-saved registers at function prologs and epilogs instead of mov instructions to and
         from memory locations based off the stack pointer. The default is ON when the CPU target
         is barcelona, and OFF otherwise.</p>
      ]]>
   </flag>

   <flag name="F-CG:sse_cse_regs" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:sse_cse_regs=\d+">
      <example>-CG:sse_cse_regs</example>
      <![CDATA[
         <p>-CG:sse_cse_regs=N : When performing common subexpression elimination during
        code  generation, assume there are N extra SSE registers available over the number
        provided by the CPU.  N can  be  positive,  zero,  or  negative.   The
        default is positive infinity.</p>
      ]]>
   </flag>

  <flag name="F-CG:use_prefetchnta" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-CG:use_prefetchnta=(0|1|off|on)">
      <example>-CG:use_prefetchnta</example>
      <![CDATA[
         <p>-CG:use_prefetchnta: Prefetch when data is non-temporal at all levels of the cache
           hierarchy. This is for data streaming situations in which the
           data will not need to be re-used soon. The default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-INLINE:aggressive" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-INLINE:aggressive=(on|off|0|1)">
      <example>-INLINE:aggressive</example>
      <![CDATA[
         <p>-INLINE:aggressive : Tell the compiler to be more aggressive about inlining.
           The default is -INLINE:aggressive=OFF.</p>
      ]]>
   </flag>

   <!-- Sub-flags of the -IPA: group -->

   <flag name="F-IPA:callee_limit" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-IPA:callee_limit=\d+">
      <example>-IPA:callee_limit</example>
      <![CDATA[
         <p>The inter-procedural analyzer option group -IPA: controls
         application of inter-procedural analysis and optimization.</p>

         <p>-IPA:callee_limit=N : Functions whose size exceeds this limit
         will never be automatically inlined by the compiler.
         The default is 500.</p>
      ]]>
   </flag>

   <flag name="F-IPA:linear" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-IPA:linear=(on|off|0|1)">
      <example>-IPA:linear</example>
      <![CDATA[
         <p>-IPA:linear : Controls conversion of a multi-dimensional array
         to a single dimensional (linear) array that covers the same block
         of memory. When inlining Fortran subroutines, IPA tries to map
         formal array parameters to the shape of the actual parameter.
         In the case that it cannot map the parameter, it linearizes
         the array reference. By default, IPA will not inline such callsites
         because they may cause performance problems.
         The default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-IPA:plimit" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-IPA:plimit=\d+">
      <example>-IPA:plimit</example>
      <![CDATA[
         <p>-IPA:plimit=N : This option stops inlining into a specific
         subprogram once it reaches size N in the intermediate representation.
         Default is 2500.</p>
      ]]>
   </flag>

   <flag name="F-IPA:pu_reorder" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-IPA:pu_reorder=[0-2]">
      <example>-IPA:pu_reorder</example>
      <![CDATA[
         <p>-IPA:pu_reorder=N : Control re-ordering the layout of program units
         based on their invocation patterns in feedback compilation to minimize
         instruction cache misses.
         This option is ignored unless under feedback compilation.</p>

         <p style="text-indent: -25px; margin-left: 25px">
            0&nbsp;&nbsp;&nbsp; Disable procedure reordering.
            This is the default for non-C++ programs.</p>

         <p style="text-indent: -25px; margin-left: 25px">
            1&nbsp;&nbsp;&nbsp; Reorder based on the frequency
            in which different procedures are invoked.
            This is the default for C++ programs.</p>

         <p style="text-indent: -25px; margin-left: 25px">
            2&nbsp;&nbsp;&nbsp; Reorder based on caller-callee
            relationship.</p>
      ]]>
   </flag>

   <flag name="F-IPA:space" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-IPA:space=\d+">
      <example>-IPA:space</example>
      <![CDATA[
         <p>-IPA:space=N : Inline until a program expansion of N % is reached.
         For example, -IPA:space=20 limits code expansion due to inlining
         to approximately 20 %. Default is no limit.</p>
      ]]>
   </flag>

   <!-- Sub-flags of the -LNO group -->

   <flag name="F-LNO:blocking" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:blocking=(on|off|0|1)\b">
      <example>-LNO:blocking</example>
      <![CDATA[
         <p>Specify options and transformations performed on loop nests
         by the Loop Nest Optimizer (LNO). The -LNO options are enabled only
         if -O3 is also specified on the pathf95 command line.</p>

         <p>-LNO:blocking : Enable or disable the cache blocking transformation.
         The default is ON.</p>
      ]]>
   </flag>

   <flag name="F-LNO:full_unroll" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:(full_unroll|fu)=\d+\b">
      <example>-LNO:full_unroll</example>
      <![CDATA[
         <p>-LNO:full_unroll,fu=N : Fully unroll loops with trip_count <= N
         inside LNO. N can be any integer between 0 and 100.
         The default value for N is 5. Setting this flag to 0 disables
         full unrolling of small trip count loops inside LNO.</p>
      ]]>
   </flag>

   <flag name="F-LNO:full_unroll_outer" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:full_unroll_outer=(on|off|0|1)\b">
      <example>-LNO:full_unroll_outer</example>
      <![CDATA[
         <p>-LNO:full_unroll_outer=(on|off|0|1) : Control  the  full unrolling of loops with
         known trip count that do not contain a loop
        and are not contained in a loop. The conditions implied by both the  full_unroll  and
        the  full_unroll_size options must be satisfied for the loop to be fully unrolled. The
        default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-LNO:full_unroll_size" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:full_unroll_size=\d+\b">
      <example>-LNO:full_unroll_size</example>
      <![CDATA[
         <p>-LNO:full_unroll_size=N : Fully  unroll  loops  with  unrolled  loop
         size <= N inside LNO. N can be any integer
        between 0 and 10000. The conditions implied by the full_unroll  option  must  also  be
        satisfied for the loop to be fully unrolled. The default value for N is 2000.</p>
      ]]>
   </flag>

   <flag name="F-LNO:fission" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:fission=[0-2]\b">
      <example>-LNO:fission</example>
      <![CDATA[
         <p>-LNO:fission=N : Perform loop fission. N can be one of the following:<br>
         0 = Disable loop fission (default)<br>
         1 = Perform normal loop fission as necessary<br>
         2 = Specify that fission be tried before fusion<br></p>
         <p> Because  -LNO:fusion is on by default, turning on fission without turning off
            fusion may result in their effects being nullified.   Ordinarily, fusion  is
            applied  before  fission.   Specifying  -LNO:fission=2  will turn on fission and
            cause it to be applied before fusion.</p>
      ]]>
   </flag>

   <flag name="F-LNO:fusion" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:fusion=[0-2]\b">
      <example>-LNO:fusion</example>
      <![CDATA[
         <p>-LNO:fusion=N : Perform loop fusion. N can be one of the following:<br>
         0 = Loop fusion is off<br>
         1 = Perform conservative loop fusion<br>
         2 = Perform aggressive loop fusion<br>
         The default is 1.</p>
      ]]>
   </flag>

   <flag name="F-LNO:ignore_feedback" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:ignore_feedback=(on|off|0|1)\b">
      <example>-LNO:ignore_feedback</example>
      <![CDATA[
         <p>-LNO:ignore_feedback=(on|off|0|1) : If the flag is ON then feedback information
         from the loop annotations will be ignored in LNO transformations.
         The default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-LNO:interchange" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:interchange=(on|off|0|1)\b">
      <example>-LNO:interchange</example>
      <![CDATA[
         <p>-LNO:interchange=(on|off|0|1) : Disable the loop interchange transformation in the
         loop nest optimizer. Default is ON.
         </p>
      ]]>
   </flag>

   <flag name="F-LNO:minvariant" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:minvariant=(on|off|0|1)\b">
      <example>-LNO:minvariant</example>
      <![CDATA[
         <p>Enable or disable moving loop-invariant expressions out
         of loops. The default is ON.</p>
      ]]>
   </flag>

   <flag name="F-LNO:opt" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:opt=(0|1)\b">
      <example>-LNO:opt=0</example>
      <![CDATA[
         <p>This option controls the LNO optimization level. The  options  can  be
           one of the following:<br>
           0 = Disable nearly all loop nest optimizations.<br>
           1 = Perform full loop nest transformations. This is the default.</p>
      ]]>
   </flag>

  <flag name="F-LNO:outer_unroll_max" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:(outer_unroll_max|ou_max)=\d+\b">
      <example>-LNO:outer_unroll_max</example>
      <![CDATA[
         <p>-LNO:outer_unroll_max,ou_max=N : The Outer_unroll_max option indicates that the com-
          piler may unroll outer loops in a loop nest by as many as N per loop, but no more.
          The default is 5.</p>
      ]]>
   </flag>

   <flag name="F-LNO:ou_prod_max" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:ou_prod_max=\d+\b">
      <example>-LNO:ou_prod_max</example>
      <![CDATA[
         <p>-LNO:ou_prod_max=N : This option indicates that the product
         of unrolling of the various outer loops in a given loop nest
         is not to exceed N, where N is a positive integer.
         The default is 16.</p>
      ]]>
   </flag>

   <flag name="F-LNO:prefetch_ahead" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:prefetch_ahead=\d+\b">
      <example>-LNO:prefetch_ahead</example>
      <![CDATA[
         <p>-LNO:prefetch_ahead=N : Prefetch N cache line(s) ahead.
         The default is 2.</p>
      ]]>
   </flag>

   <flag name="F-LNO:prefetch" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:prefetch=[0-3]\b">
      <example>-LNO:prefetch</example>
      <![CDATA[
         <p>-LNO:prefetch=(0|1|2|3) : This option specifies
         the level of prefetching.</p>

         <p>0 = Prefetch disabled.</p>

         <p>1 = Prefetch is done only for arrays that are always referenced
         in each iteration of a loop.</p>

         <p>2 = Prefetch is done without the above restriction.
         This is the default.</p>

         <p> 3 = Most aggressive.</p>
          ]]>
   </flag>

   <flag name="F-LNO:pf2" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:pf2=(on|off|0|1)\b">
      <example>-LNO:pf2</example>
      <![CDATA[
         <p>This option selectively disables or enables prefetching for Level 2 cache. The default
            is ON</p>
      ]]>
   </flag>

   <flag name="F-LNO:sclrze" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:sclrze=(on|off)\b">
      <example>-LNO:sclrze</example>
      <![CDATA[
         <p>Turn ON or OFF the optimization that replaces an array by a
         scalar variable. The default is ON.</p>
      ]]>
   </flag>

   <flag name="F-LNO:simd" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:simd=[0-2]\b">
      <example>-LNO:simd</example>
      <![CDATA[
         <p>-LNO:simd=(0|1|2) : This option enables or disables
         inner loop vectorization.</p>

         <p>0 = Turn off the vectorizer.</p>

         <p>1 = (Default) Vectorize only if the compiler can determine that
         there is no undesirable performance impact due to sub-optimal
         alignment. Vectorize only if vectorization does not introduce
         accuracy problems with floating-point operations.</p>

         <p>2 = Vectorize without any constraints (most aggressive).</p>
      ]]>
   </flag>

   <flag name="F-LNO:trip_count" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:trip_count=\d+\b">
      <example>-LNO:trip_count</example>
      <![CDATA[
         <p>-LNO:trip_count=N : This flag is to provide an assumed loop trip-count if
            it  is unknown at compile time. LNO uses this information for loop
            transformations and prefetch, etc. N can be any positive integer, and
            the default value is 1000.</p>
      ]]>
   </flag>

   <flag name="F-LNO:vintr" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LNO:vintr=[0-2]\b">
      <example>-LNO:vintr</example>
      <![CDATA[
         <p>-LNO:vintr=(0|1|2) : This  flag controls loop vectorization to make use of vector intrinsic
        routines (Note: a vector intrinsic routine is called once to compute a
        math  intrinsic  for  the entire vector). -LNO:vintr=1 is the default.
        -LNO:vintr=0 turns off the vintr optimization. Under -LNO:vintr=2  the
        compiler will do aggressive optimization for all vector intrinsic rou-
        tines.  Note that -LNO:vintr=2 could be unsafe in that some  of  these
        routines could have accuracy problems.
         </p>
      ]]>
   </flag>

   <!-- Individual subflags of the -OPT: class -->

   <flag name="F-OPT:alias" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:alias=(typed|restrict|disjoint|no_f90_pointer_alias)\b">
       <example>-OPT:alias</example>
      <![CDATA[
         <p>The -OPT: option group controls miscellaneous optimizations.
         These options override defaults based on the main
         optimization level.</p>

         <p>-OPT:alias=&lt;name&gt;<br>
         Specify the pointer aliasing model
         to be used. By specifying one or more of the following for &lt;name&gt;,
         the compiler is able to make assumptions throughout the compilation:</p>

         <p style="text-indent: -25px; margin-left: 25px">
         typed<br>
            Assume that the code adheres to the ANSI/ISO C standard
            which states that two pointers of different types cannot point
            to the same location in  memory.
            This is ON by default when -OPT:Ofast is specified.</p>

         <p style="text-indent: -25px; margin-left: 25px">
         restrict<br>
            Specify that distinct pointers are assumed to point to distinct,
            non-overlapping objects. This is OFF by default.</p>

         <p style="text-indent: -25px; margin-left: 25px">
         disjoint<br>
            Specify that any two pointer expressions are assumed to point
            to distinct, non-overlapping objects. This is OFF by default.</p>

         <p style="text-indent: -25px; margin-left: 25px">
         no_f90_pointer_alias<br>
            Specify that any two Fortran 90 pointer expressions are assumed to point
            to distinct, non-overlapping objects. This is OFF by default.</p>
      ]]>
   </flag>

   <flag name="F-OPT:div_split" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:div_split=(on|off|0|1)\b">
       <example>-OPT:div_split</example>
      <![CDATA[
         <p>-OPT:div_split=(ON|OFF)<br>
         Enable or disable changing x/y into x*(recip(y)). This is OFF by
         default, but enabled by -OPT:Ofast or -OPT:IEEE_arithmetic=3.
         This transformation generates fairly accurate code.</p>
      ]]>
   </flag>

   <flag name="F-OPT:fast_complex" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:fast_complex=(on|off|0|1)\b">
       <example>-OPT:fast_complex</example>
      <![CDATA[
         <p>-OPT:fast_complex<br>
         Setting fast_complex=ON enables fast
         calculations for values declared to be of the type complex.
         When this is set to ON, complex absolute value (norm) and complex
         division use fast algorithms that overflow for an operand
         (the divisor, in the case of division) that has an absolute value
         that is larger than the square root of the largest representable
         floating-point number.
         This would also apply to an underflow for a value that is smaller
         than the square root of the smallest representable floating point
         number.<br>
         OFF is the default.<br>
         fast_complex=ON is enabled if -OPT:roundoff=3 is in effect.</p>
      ]]>
   </flag>

   <flag name="F-OPT:goto" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:goto=(on|off|0|1)\b">
       <example>-OPT:goto</example>
      <![CDATA[
         <p>-OPT:goto<br>
         Disable or enable the conversion of GOTOs into higher-level
         structures like FOR loops. The default is ON for -O2 or higher.
         </p>
      ]]>
   </flag>


   <flag name="F-OPT:IEEE_arith" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:(IEEE_arithmetic|IEEE_arith|IEEE_a)=[1-3]\b">
       <example>-OPT:IEEE_arithmetic</example>
      <![CDATA[
         <p>-OPT:IEEE_arithmetic,IEEE_arith,IEEE_a=(1|2|3)<br>
         Specify the level of conformance to IEEE 754 floating pointing
         roundoff/overflow behavior.
         The options can be one of the following:</p>

         <p>1 Adhere to IEEE accuracy. This is the default when optimization
         levels -O0, -O1 and -O2 are in effect.</p>

         <p>2 May produce inexact result not conforming to IEEE 754.
         This is the default when -O3 is in effect.</p>

         <p>3 All mathematically valid transformations are allowed.</p>
      ]]>
   </flag>

   <flag name="F-OPT:malloc_alg" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:malloc_alg=[0-1]\b">
       <example>-OPT:malloc_alg</example>
      <![CDATA[
         <p>-OPT:malloc_alg=(0|1)<br>
         Select an alternate malloc algorithm which may improve speed.
         The compiler adds setup code in the
         C/C++/Fortran "main" function to enable the chosen algorithm.
         The default is 1 when -OPT:Ofast is specified. Otherwise, the default
         is 0.
         </p>
      ]]>
   </flag>

   <flag name="F-OPT:Ofast" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:Ofast\b">
       <example>-OPT:Ofast</example>
      <![CDATA[
         <p>-OPT:Ofast<br>
         Use optimizations selected to maximize performance.
         Although the optimizations are generally safe, they may affect
         floating point accuracy due to rearrangement of computations.
         This effectively turns on the following optimizations:
         -OPT:ro=2:Olimit=0:div_split=ON:alias=typed:malloc_alg=1.</p>
      ]]>
      <include flag="F-OPT:ro"/>
      <include flag="F-OPT:Olimit"/>
      <include flag="F-OPT:div_split"/>
      <include flag="F-OPT:alias"/>
      <include flag="F-OPT:malloc_alg"/>
   </flag>

   <flag name="F-OPT:Olimit" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:Olimit=(\d+)">
       <example>-OPT:Olimit</example>
      <![CDATA[
         <p>-OPT:Olimit=N<br>
         Disable optimization when size of program unit is > N. When N is 0,
         program unit size is ignored and optimization process will not be
         disabled due to compile time limit.
         The default is 0 when -OPT:Ofast is specified,
         9000 when -O3 is specified; otherwise the default is 6000.</p>
      ]]>
   </flag>

   <flag name="F-OPT:ro" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:(roundoff|ro)=[0-3]">
       <example>-OPT:ro</example>
      <![CDATA[
         <p>-OPT:roundoff,ro=(0|1|2|3)<br>
         Specify the level of acceptable departure from source language
         floating-point, round-off, and overflow semantics.
         The options can be one of the following:</p>

         <p>0 = Inhibit optimizations that might affect the floating-point
         behavior. This is the default when optimization levels -O0, -O1,
         and -O2 are in effect.</p>

         <p>1 = Allow simple transformations that might cause limited
         round-off or overflow differences. Compounding such transformations
         could have more extensive effects.
         This is the default when -O3 is in effect.</p>

         <p>2 = Allow more extensive transformations, such as the
         reordering of reduction loops.
         This is the default level when -OPT:Ofast is specified.</p>

         <p>3 = Enable any mathematically valid transformation.</p>
      ]]>
   </flag>

   <flag name="F-OPT:rsqrt" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:rsqrt=[0-2]\b">
       <example>-OPT:rsqrt</example>
      <![CDATA[
         <p>-OPT:rsqrt=(0|1|2)<br>
         This option specifies if the RSQRT machine instruction should be used
         to calculate reciprocal square root. RSQRT is faster but potentially
         less accurate than the regular square root operation.<br>
         0 means not to use RSQRT.<br>
         1 means to use RSQRT followed by instructions to refine the result.<br>
         2 means to use RSQRT by itself.<br>
         Default is 1 when -OPT:roundoff=2 or greater, else the default is 0.</p>
      ]]>
   </flag>

  <flag name="F-OPT:treeheight" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:treeheight=((on|off|0|1)\b)">
       <example>-OPT:treeheight</example>
      <![CDATA[
         <p>-OPT:treeheight=(ON|OFF)<br>
         The value ON enables re-association in expressions to reduce
         the expressions' tree height. The default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-OPT:unroll_size" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:unroll_size=(\d+)">
       <example>-OPT:unroll_size</example>
      <![CDATA[
         <p>-OPT:unroll_size=N<br>
         Set the ceiling of maximum number of instructions for  an
         unrolled  inner loop. If N=0, the ceiling is disregarded.
         The default is 40.</p>
      ]]>
   </flag>

   <flag name="F-OPT:unroll_times_max" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-OPT:(unroll_times_max|unroll_times)=(\d+)">
       <example>-OPT:unroll_times_max</example>
      <![CDATA[
         <p>-OPT:unroll_times_max=N<br>
         Unroll  inner loops by a maximum of N.  The default is 4.</p>
      ]]>
   </flag>

   <!-- Individual subflags of the -WOPT: class -->

   <flag name="F-WOPT:aggstr" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-WOPT:aggstr=\d+">
      <example>-WOPT:aggstr</example>
      <![CDATA[
         <p>The -WOPT: Specifies options that affect the global optimizer.
         The options are enabled at -O2 or above.</p>

         <p>-WOPT:aggstr=N<br>
         This controls the aggressiveness of the strength reduction optimization
         performed by the scalar optimizer, in which induction expressions
         within a loop are replaced by temporaries that are incremented
         together with the loop variable. When strength reduction is overdone,
         the additional temporaries increase register pressure, resulting in
         excessive register spills that decrease performance.
         The value specified must be a positive integer value, which specifies
         the maximum number of induction expressions that will be strength-reduced
         across an index variable increment.
         When set at 0, strength reduction is only performed for non-trivial
         induction expressions. The default is 11.</p>
      ]]>
   </flag>

   <flag name="F-WOPT:if_conv" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-WOPT:if_conv=(0|1|2)">
      <example>-WOPT:if_conv</example>
      <![CDATA[
         <p>-WOPT:if_conv=(0|1|2):<br>
         Controls  the  optimization  that translates simple IF
         statements to conditional  move  instructions  in  the
         target CPU. Setting to 0 suppresses this optimization.
         The value of 1 designates conservative  if-conversion,
         in  which  the context around the IF statement is used
         in deciding whether to  if-convert.  The  value  of  2
         enables  aggressive  if-conversion by causing it to be
         performed regardless of the context. The default is 1.</p>
      ]]>
   </flag>

   <flag name="F-WOPT:mem_opnds" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-WOPT:mem_opnds=(on|off|0|1)\b">
      <example>-WOPT:mem_opnds</example>
      <![CDATA[
         <p>-WOPT:mem_opnds=(ON|OFF)<br>
         Makes  the scalar optimizer preserve any memory operands of arithmetic
         operations so as to help bring about subsumption of memory loads into
         the operands of arithmetic operations. Load subsumption is the combining
         of an arithmetic instruction and a memory load into one instruction.
         Default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-WOPT:retype_expr" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-WOPT:retype_expr=(on|off|0|1)\b">
      <example>-WOPT:retype_expr</example>
      <![CDATA[
         <p>-WOPT:retype_expr=(ON|OFF)<br>
        Enables the optimization in the compiler that converts 64-bit address
        computation to use 32-bit arithmetic as much as possible.
        Default is OFF.</p>
      ]]>
   </flag>

   <flag name="F-WOPT:unroll" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-WOPT:unroll=(0|1|2)\b">
      <example>-WOPT:unroll</example>
      <![CDATA[
         <p>Control the unrolling of innermost loops in the scalar optimizer.
            Setting to 0 suppresses this unroller. The default is 1, which makes
            the scalar optimizer unroll only loops that contain IF statements.
            Setting to  2 makes the unrolling to also apply to loop bodies that are
            straight line code, which duplicates the unrolling done in the code
            generator, and is thus unnecessary.  The default setting of 1 makes this
            unrolling complementary to what is done in the code generator.
            This unrolling is not affected by the unrolling options under the
            -OPT group.</p>
      ]]>
   </flag>

     <!-- Individual subflags of the -GRA: class -->

     <flag name="F-GRA:optimize_boundary" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-GRA:optimize_boundary=(on|off|0|1)\b">
      <example>-GRA:optimize_boundary</example>
      <![CDATA[
       <p>The -GRA: Option group for Global Register Allocator.</p>

         <p>-GRA:optimize_boundary=(ON|OFF)<br>
        Allow the Global Register Allocator to allocate the same register to different variables
        in the same basic-block.  Default is OFF.</p>
      ]]>
   </flag>

    <!-- Individual subflags of the -LANG: class -->

    <flag name="F-LANG:copyinout" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-LANG:copyinout=(on|off)">
      <example>-LANG:copyinout</example>
      <![CDATA[
         <p>The -LANG: This controls the language option group.</p>

         <p>-LANG:copyinout=(ON|OFF)<br>
         When an array section is passed as the actual argument in a call, the compiler sometimes copies the
         array section to a temporary array and passes the temporary array, thus promoting locality in the
         accesses to the array argument. This optimization is relevant only to Fortran, and this flag controls
         the aggressiveness of this optimization.  The default is ON for -O2 or higher and OFF otherwise.</p>
      ]]>
   </flag>

   <!-- Individual subflags of the -TENV: class -->

   <flag name="F-TENV:frame_pointer" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-TENV:frame_pointer=(on|off)">
      <example>-TENV:frame_pointer</example>
      <![CDATA[
         <p>The -TENV: This option specifies the target environment option group. These options control the
            target environment  assumed  and/or produced by the compiler </p>

         <p>-TENV:frame_pointer=(ON|OFF)<br>
         Default is ON for C++ and OFF otherwise. Local variables in the function stack frame are addressed
         via  the  frame pointer register. Ordinarily, the compiler will replace this use of frame pointer by
         addressing local variables via the stack pointer when it determines that the stack pointer is fixed
         throughout the function invocation. This frees up the frame pointer for other purposes. Turning this
         flag on forces the compiler to use the frame pointer to address local variables. This flag defaults
         to ON for C++ because the exception handling mechanism relies on the frame pointer register being
         used to address local variables. This flag can be turned OFF for C++ for programs that do not throw
         exceptions.</p>
      ]]>
   </flag>

   <!-- Linker flags -->

   <flag name="Bstatic" class="optimization"
         compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
         regexp="-Bstatic\b">
      <![CDATA[
         <p>Link with static libraries.</p>
      ]]>
   </flag>

   <flag name="Bstatic_pgi" class="optimization"
         compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
         regexp="-Bstatic_pgi\b">
      <![CDATA[
         <p>Staticily link with the PGI runtime libraries.
         System libraries may still be dynamically linked.</p>
      ]]>
   </flag>

   <flag name="Bdynamic_lin" class="optimization"
         compilers="C_PGI, Cplusplus_PGI, Fortran_PGI"
         regexp="-Bdynamic\b">
      <![CDATA[
         <p>Link with dynamic libraries.</p>
      ]]>
   </flag>

   <flag name="F-static" class="optimization"
         compilers="C_PathScale, Cplusplus_PathScale, Fortran_PathScale"
         regexp="-static">
       <example>-static</example>
      <![CDATA[
         <p>-static<br>
         Suppress dynamic linking at runtime for shared libraries;
         use static linking instead.</p>
      ]]>
   </flag>

   <flag name="Link_path" class="other"
         regexp="-L\S+\b">
      <![CDATA[
         <p>Specifies a directory to search for libraries.
         Use -L to add directories to the search path for library files.
         Multiple -L options are valid. However, the position of multiple -L options
         is important relative to -l options supplied.</p>
      ]]>
      <example>-L/path/to/libs</example>
   </flag>

   <flag name="SmartHeap_lin" class="optimization"
         regexp="-lsmartheap\b">
      <![CDATA[
         <p>Link using <a href=http://www.microquill.com/>MicroQuill's</a> SmartHeap 8 (32-bit) library
         for Linux. Description from Microquill: </p>
         <p>SmartHeap is a fast (3X-100X faster than compiler-supplied libraries),
         portable (Windows, Linux, Solaris, HP-UX, IBM-AIX, Dec OSF Tru64, SGI Irix),
         reliable, ANSI-compliant malloc/operator new library.
         SmartHeap supports multiple memory pools, includes a fixed-size allocator, and is thread-safe.
         SmartHeap also includes comprehensive memory debugging APIs to detect leakage, overwrites,
         double-frees, wild pointers, out of memory, references to previously freed memory,
         and other memory errors.
         </p>
      ]]>
   </flag>

   <!-- End of description of flag groups -->

   <!-- End of description of optimization flags -->
	
<!-- /OPTIMIZATION -->

</flagsdescription>
