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

<!-- The lines above are NOT optional.  If you're adept at reading DTDs,
     the one that this file conforms to is at the URL listed above.  
     
     But most humans writing a flags file will want to have it automatically 
     checked using a validating parser such as RXP (available at
     http://www.ltg.ed.ac.uk/~richard/rxp.html), or use one of the on-line
     parsers:
       http://www.stg.brown.edu/service/xmlvalid/
       http://www.cogsci.ed.ac.uk/~richard/xml-check.html
     
     The parser used by the CPU tools is _not_ a validating parser, so it
     may be possible to sneak things by it that would not pass the checkers
     above.  However, if the checkers above say that your file is clean, it's
     clean.

     Flag files submitted to SPEC _will_ be checked by a validating parser.
     Invalid or not-well-formed flag files will be rejected.

     This file is
       Copyright (C) 2006 Standard Performance Evaluation Corporation
       All Rights Reserved
     
     This file may be freely modified and redistributed, provided that the
     copyright notice above and this notice remain unaltered.

     $Id: flags-simple.xml 4007 2006-03-17 11:34:42Z cloyce $

     **********************************************************************
     **********************************************************************
     Unless otherwise explicitly noted, all references to "section n.nn"
     refer to flag_description.html, available at

     http://www.spec.org/cpu2006/docs/flag_description.html
     **********************************************************************
     **********************************************************************

	NOTES:

		
-->
<flagsdescription>

<filename>IBM-AIX</filename>

<title>IBM AIX: Environment Settings and Utilities</title>

<style>
<![CDATA[
body { background: white; }
]]>
</style>

<!-- =====================================================================
  The <header> section is also entirely optional.  If it is provided, and
  no class is specified, then it will be inserted verbatim at the top
  of the flags dump.

  If a class is specified, that text will be inserted verbatim before flags
  of that class.  
  
  As the contents should be HTML, it will save lots of time to just enclose
  the whole thing in a CDATA section.  Section 2.3.1 again.
     ===================================================================-->
<header>
<![CDATA[
<p>IBM AIX 5L V5.3</p>
<p>IBM AIX V6</p>
<p>Last updated: 03-Oct-2008</p> ]]>
</header>

<!-- =====================================================================
  Information about the meaning of boot-time settings, BIOS options,
  kernel tuning, and so forth can go in the 'platform_settings' section.

  They'll be appended to the end of both the flags dump and per-result flag report.

  As the contents should be HTML, it will save lots of time to just enclose
  the whole thing in a CDATA section.  Section 2.3.1 again.
     ===================================================================-->
<platform_settings>
<![CDATA[
<ul>
<li> drmgr -r -c cpu </li> Deconfigures one core from the active partition. Use it N times to deconfigure N cores.</p>
<li> smtctl -m on|off -w now|boot</li> <br />Controls the enabling and disabling of processor simultaneous multi-threading mode.</p>
<li> vmo -r -o lgpg_regions=n -o lgpg_size=16777216</li> <br />Sets the size of large pages to 16M, and set the number to use, with -r, takes effect on the next IPL.</p>
<li> bosboot -q</li> <br />Regenerates the IPL boot to set the options specified with smtctl and vmo.</p>
<li> ulimit </li> <br />Controls resources allowed to be used by processes.  All resource are set to unlimited, of primary importance is the "stack" and "data/heap" settings for SPEC CPU2006 and MPI2007.</p>
<li> chsyscfg -m <tt>system</tt> -r prof -i name=<tt>profile</tt>,lpar_name=<tt>partition</tt>,lpar_proc_compat_mode=POWER6_enhanced</li> <br />This command enables the POWERPC architecture optional instructions supported on POWER6.</p>
<pre>
Usage: chsyscfg -r lpar | prof | sys | sysprof | frame
                -m &lt;managed system&gt; | -e &lt;managed frame&gt;
                -f &lt;configuration file&gt; | -i "&lt;configuration data&gt;"
                [--help]

Changes partitions, partition profiles, system profiles, or the attributes of a
managed system or a managed frame.

    -r                        - the type of resource(s) to be changed:
                                  lpar    - partition
                                  prof    - partition profile
                                  sys     - managed system
                                  sysprof - system profile
                                  frame   - managed frame
    -m &lt;managed system&gt;       - the managed system's name
    -e &lt;managed frame&gt;        - the managed frame's name
    -f &lt;configuration file&gt;   - the name of the file containing the
                                configuration data for this command.
                                The format is:
                                  attr_name1=value,attr_name2=value,...
                                or
                                  "attr_name1=value1,value2,...",...
    -i "&lt;configuration data&gt;" - the configuration data for this command.
                                The format is:
                                  "attr_name1=value,attr_name2=value,..."
                                or
                                  ""attr_name1=value1,value2,...",..."
    --help                    - prints this help

The valid attribute names for this command are:
    -r prof     required: name, lpar_id | lpar_name
                optional: ...
                          lpar_proc_compat_mode (default | POWER6_enhanced)
</pre>
<li> bindprocessor $$ &lt;n&gt; </li> <br />The next program is to be bound to the specified processor.</p>
<p> Environment variables set before the run:</p>
<li> MEMORY_AFFINITY=MCM </li><br />Cause the OS to alloc memory "closest" to the chip that first requests it.</p>
<li> MALLOCOPTIONS=POOL </li><br />Selects the OS malloc option that allocates/frees small objects very quickly.</p>
<li> XLFRTEOPTS=intrinthrds=1 </li><br />Causes the Fortran runtime to only use a single thread.</p>
</ul>
]]>
</platform_settings>


<!--
  -
  -	Optimization flags: memory allocation.
  -
  -->

<flag name="F-bmaxdata"
      class="optimization"
      regexp="-bmaxdata:(\S+)\b">
<example>
-bmaxdata:0x20000000,
-bmaxdata:0x40000000,
-bmaxdata:0x50000000,
-bmaxdata:0x60000000,
-bmaxdata:0x80000000
</example>
Causes the system loader to put the heap in it's own segment of the size specified.
This is only required for 32-bit applications, as their segments are 256M. If the
last digit of the value is "C", then it also turns off the malloc pool option for
that executable.
</flag>


<flag name="F-bdatapsize"
      class="optimization"
      regexp="-bdatapsize:64K\b">
<example>
-bdatapsize:64K
</example>
Specifies a non-default page size of 64K for the program data segment.
</flag>


<flag name="F-bstackpsize"
      class="optimization"
      regexp="-bstackpsize:64K\b">
<example>
-bstackpsize:64K
</example>
Specifies a non-default page size of 64K for the program stack segment.
</flag>


<flag name="F-btextpsize"
      class="optimization"
      regexp="-btextpsize:64K\b">
<example>
-btextpsize:64K
</example>
Specifies a non-default page size of 64K for the program text segment.
</flag>


<flag name="F-blpdata"
      class="optimization"
      regexp="-blpdata\b">
Sets the bit in the file's XCOFF header indicating that this
executable will request the use of large pages when they are
available on the system and when the user has an appropriate
privilege
</flag>



<!--
  -
  -	Optimization flags: vector calculations.
  -
  -->

<flag name="F-D__IBM_FAST_VECTOR"
      class="optimization"
      regexp="-D__IBM_FAST_VECTOR\b">
The __IBM_FAST_VECTOR macro defines a different iterator for the std::vector
template class. This iterator results in faster code, but is not compatible
with code using the default iterator for a std::vector template class.
All uses of std::vector for a data type must use the same iterator.
 Add -D__IBM_FAST_VECTOR to the compile line, or "#define __IBM_FAST_VECTOR 1"
to your source code to use the faster iterator for std::vector template class.
 You must compile all sources with this macro.
</flag>


<flag name="F-D__IBM_FAST_SET_MAP_ITERATOR"
      class="optimization"
      regexp="-D__IBM_FAST_SET_MAP_ITERATOR\b">
The __IBM_FAST_SET_MAP_ITERATOR macro defines a different iterator for the
std::vector template class. This iterator results in faster code, but is not
compatible with code using the default iterator for a std::vector template class.
All uses of std::vector for a data type must use the same iterator.
 Add -D__IBM_FAST_SET_MAP_ITERATOR to the compile line, or
 "#define __IBM_FAST_SET_MAP_ITERATOR 1" to your source code to use the
 faster iterator for std::vector template class.
You must compile all sources with this macro.
</flag>



<!--
  -
  -	Optimization flags: support libraries.
  -
  -->

<flag name="F-D_ILS_MACROS"
      class="optimization"
      regexp="-D_ILS_MACROS\b">
Causes AIX to define "ischar()" (and friends) as macro's and not subroutines.
</flag>


</flagsdescription>