CPU2006 Flag Description
Fujitsu Siemens Computers PRIMERGY RX100 S4, Intel Xeon processor 3050, 2.13 GHz

Compilers: Intel Compilers for C++ and Fortran, Version 9.1 for IA32/EM64T-based applications in Linux_x64
Operating system: 64-bit SUSE Linux 10 Enterprise Edition
Last updated: 27-Mar-2007 PS

The text for many of the descriptions below was taken from the documentation of the Intel Compilers. This documentation is copyright © 2006 Intel Corporation. All Rights Reserved.
The original documentation is distributed with the Intel compilers.



Base Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C


Peak Compiler Invocation

C benchmarks

C++ benchmarks (except as noted below)

450.soplex

Fortran benchmarks (except as noted below)

434.zeusmp

Benchmarks using both Fortran and C


Base Portability Flags

410.bwaves

416.gamess

433.milc

434.zeusmp

435.gromacs

436.cactusADM

437.leslie3d

444.namd

447.dealII

450.soplex

453.povray

454.calculix

459.GemsFDTD

465.tonto

470.lbm

481.wrf

482.sphinx3


Peak Portability Flags

410.bwaves

416.gamess

435.gromacs

436.cactusADM

437.leslie3d

444.namd

447.dealII

453.povray

454.calculix

459.GemsFDTD

465.tonto

481.wrf


Base Optimization Flags

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C


Peak Optimization Flags

C benchmarks

433.milc

470.lbm

482.sphinx3

C++ benchmarks

444.namd

447.dealII

450.soplex

453.povray

Fortran benchmarks

410.bwaves

416.gamess

434.zeusmp

437.leslie3d

459.GemsFDTD

465.tonto

Benchmarks using both Fortran and C

435.gromacs

436.cactusADM

454.calculix

481.wrf


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.


System and Other Tuning Information

Platform settings

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

Hardware Prefetch:

This BIOS option allows the enabling/disabling of a processor mechanism to prefetch data into the cache according to a pattern-recognition algorithm.

In some cases, setting this option to Disabled may improve performance. Users should only disable this option after performing application benchmarking to verify improved performance in their environment.

Adjacent Sector Prefetch:

This BIOS option allows the enabling/disabling of a processor mechanism to fetch the adjacent cache line within an 128-byte sector that contains the data needed due to a cache line miss.

In some cases, setting this option to Disabled may improve performance. Users should only disable this option after performing application benchmarking to verify improved performance in their environment.

-I

Compiler option to set the path for include files.
Used in some integer peak benchmarks which were built using the Intel 64-bit compiler. Used in some floating point peak benchmarks which were built using the Intel 32-bit compiler.

-L

Compiler option to set the path for library files.
Used in some integer peak benchmarks which were built using the Intel 64-bit compiler. Used in some floating point peak benchmarks which were built using the Intel 32-bit compiler.

ulimit -s

Sets the stack size to n kbytes, or unlimited to allow the stack size to grow without limit.

submit= MYMASK=`printf '0x%x' \$((1<<\$SPECCOPYNUM))`; /usr/bin/taskset \$MYMASK $command

When running multiple copies of benchmarks, the SPEC config file feature submit 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:


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 file that was used to format this result can be browsed at
http://www.spec.org/cpu2006/flags/CPU2006_flags.20090714.09.html.

You can also download the XML flags source by saving the following link:
http://www.spec.org/cpu2006/flags/CPU2006_flags.20090714.09.xml.


For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact webmaster@spec.org
Copyright 2006-2014 Standard Performance Evaluation Corporation
Tested with SPEC CPU2006 v1.0.
Report generated on Tue Jul 22 11:04:10 2014 by SPEC CPU2006 flags formatter v6906.