CPU2006 Flag Description
Oracle Corporation SPARC T7-1


Oracle Solaris Studio 12.4

  • "cc": Oracle Solaris Studio C
  • "CC": Oracle Solaris Studio C++
  • "f90": Oracle Solaris Studio Fortran
Operating systems: Solaris 10 and 11

The text for many of the descriptions below was excerpted from the Oracle Solaris Studio Compiler Documentation, which is copyright © 2015 Oracle Corporation. The original documentation can be found at http://www.oracle.com/technetwork/documentation/solaris-studio-12-192994.html.

Base Compiler Invocation

C benchmarks

C++ benchmarks

Peak Compiler Invocation

C benchmarks

C++ benchmarks

Base Portability Flags





Peak Portability Flags





Base Optimization Flags

C benchmarks

C++ benchmarks

Peak Optimization Flags

C benchmarks










C++ benchmarks




Base Other Flags

C benchmarks

C++ benchmarks

Peak Other Flags

C benchmarks

C++ benchmarks

Implicitly Included Flags

This section contains descriptions of flags that were included implicitly by other flags, but which do not have a permanent home at SPEC.

Commands and Options Used to Submit Benchmark Runs

submit=echo 'pbind -b...' > dobmk; sh dobmk (SPEC tools, Unix shell)
When running multiple copies of benchmarks, the SPEC config file feature submit is often used to cause individual jobs to be bound to specific processors. If so, the specific command may be found in the config file; here is a guide to understanding that command:

Shell, Environment, and Other Software Settings

This result has been formatted using multiple flags files. The "sw environment" from each of them appears next.

Sw environment from Oracle-Solaris-Studio12.4

Oracle Solaris SPEC CPU Flags

If set to "Y", additional memory allocation buckets will be created, so that threads will not need to share buckets unless more than 2*NCPUS threads are created. This variable is used by mtmalloc.

Sets the number of threads to use in OpenMP parallel regions.

Binds threads in an OpenMP program to the virtual processors enumerated in the assignment. Can also be set to TRUE, which casues threads to be bound in a round-robin fashion.

Specifies whether idle threads should SLEEP or SPIN.

Set the size of the stack (temporary storage area) for each slave thread of a multithreaded program.

ulimit -s <n>
Sets the stack size to n kbytes, or "unlimited" to allow the stack size to grow without limit.
Note that the "heap" and the "stack" share space; if your application allocates large amounts of memory on the heap, then you may find that the stack limit should not be set to "unlimited". A commonly used setting for SPEC CPU2006 purposes is a stack size of 128MB (131072K).

Sw environment from Oracle-Tseries-RevB

Oracle T Series Platform File

LD_LIBRARY_PATH controls the search order for both the compile-time and run-time linkers. Usually, it can be defaulted; but testers may sometimes choose to explicitly set it (as documented in the notes in the submission), in order to ensure that the correct versions of libraries are picked up.

MADV=access_lwp and LD_PRELOAD=madv.so.1
When the madv.so.1 shared object is present in the LD_PRELOAD list, it is possible to provide advice to the system about how memory is likely to be accessed. The advice present in MADV applies to all processes and their descendants. A commonly used value is access_lwp, which means that when memory is allocated, the next process to touch it will be the primary user. Examples of other possible values include sequential, for memory that is used only once and then no longer needed and acces_many when many processes will be sharing data.

MPSSHEAP=<size>, MPSSSTACK=<size>, and LD_PRELOAD=mpss.so.1
When these variables are set, the mpss.so.1 shared object will set the preferred page size for new processes, and their descendants, to the requested sizes for the heap and stack.

Operating System Tuning Parameters

Platform settings

One or more of the following settings may have been applied to the testbed. If so, the "Platform Notes" section of the report will say so; and you can read below to find out more about what these settings mean.

autoup=<n> (Unix /etc/system)
When the file system flush daemon fsflush runs, it writes to disk all modified file buffers that are more than n seconds old.

bufhwm=<n> (Unix /etc/system)
Sets the upper limit of the file system buffer cache. The units for bufhwm are in kilobytes.

cpu_bringup_set=<n> (Unix /etc/system)
Specifies which processors are enabled at boot time. <n> represents a bitmap of the processors to be brought online.

poweradm set administrative-authority=none (Unix, superuser commands)
Solaris power management settings are determined by an 'administrative-authority'. When the authority is set to 'none', Solaris does not attempt to manage power.

psrset -c <n> (Unix, superuser commands)
Creates a new processor set and displays the new processor set ID.

psrset -e <n> (Unix, superuser commands)
Executes a command (with optional arguments) in the specified processor set. The command process and any child processes are executed only by processors in the processor set.

segmap_percent=<n> (Unix /etc/system)
This value controls the size of the segmap cache as a percent of total memory. Set this value to help keep the file system cache from consuming memory unnecessarily.

STACKSIZE=<n> (Unix environment variable)
Set the size of the stack (temporary storage area) for each slave thread of a multithreaded program.

svcadm disable webconsole (Unix, superuser commands)
Turns off the Sun Web Console, a browser-based interface that performs systems management. If it is enabled, system administrators can manage systems, devices and services from remote systems.

ts_dispatch_extended=<n> (Unix /etc/system)
Controls which dispatch table is loaded upon boot. A value of 1 loads the large system table, a value of 0 loads the regular system table.

tune_t_fsflushr=<n> (Unix /etc/system)
Controls the number of seconds between runs of the file system flush daemon, fsflush.

user_reserve_hint_pct=<n> (Unix /etc/system)
Informs the system about how much memory is expected to be used by applications (as a percentage).

Firmware / BIOS / Microcode Settings

Power management policy (Integrated Lights Out Manager, ILOM)

The power management settings available from the ILOM menus, and their meanings, are:

Flag description origin markings:

[user] Indicates that the flag description came from the user flags file.
[suite] Indicates that the flag description came from the suite-wide flags file.
[benchmark] Indicates that the flag description came from a per-benchmark flags file.

The flags files that were used to format this result can be browsed at

You can also download the XML flags sources by saving the following links:

For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact webmaster@spec.org
Copyright 2006-2015 Standard Performance Evaluation Corporation
Tested with SPEC CPU2006 v1.2.
Report generated on Tue Nov 17 19:13:48 2015 by SPEC CPU2006 flags formatter v6906.