SPEC MPI2007 Config Files

(To check for possible updates to this document, please see http://www.spec.org/mpi2007/Docs/ )

Overview

Click one of the following to go to the detailed contents about that item:

I. Introduction

II. Config file options for runspec

III. Config file options for specmake

IV. Config file options for the shell

V. Config file options for readers

VI. Deprecated options

VII. The config file preprocessor

VIII. Output files - and how they relate to your config file

IX. About Alternate Sources

X. Troubleshooting

Contents

I. Introduction

A. What is a config file? (Background: benchmark philosophy.)

B. What does a config file affect?

1. runspec

2. specmake

3. The shell

4. Readers of the results

5. The config file preprocessor

C. Config file structure

1. Comments and whitespace

2. Header section

3. Named sections

a. Precedence of the benchmark specifier

Default benchmark

Named suite

Named benchmark

Order of differing sections does not matter

Order of the same section does matter

b. Precedence of the tuning specifier

c. Precedence of the extension specifier

Extension found in config file

Extension not found in config file

Extension override

d. Combining specifier types

e. Precedence among section types

4. MD5 section

5. Shell-like "here documents" and continued lines

6. Included files

D. Variable substitution

1. By runspec, at startup: $[variable]

2. By runspec, during a run: $variable and ${variable}

2. By the shell: \$VARIABLE

4. By specmake: $(VARIABLE)

5. Example: controlling rank counts in the AIX MPI driver

6. Limitations on variable substitution

7. Unsetting a variable with %undef%

II. Config file options for runspec

A. Options that can also be used on the runspec command line

action check_version delay deletework ext flagsurl http_proxy http_timeout ignore_errors info_wrap_columns iterations mach make_no_clobber nobuild notes_wrap_columns output_format ranks reportable rebuild runlist setprocgroup size table tune verbose

B. Options for runspec that can only be used in a config file

allow_extension_override backup_config basepeak build_in_build_dir check_md5 command_add_redirect difflines env_vars expand_notes expid fail fail_build fail_run ignore_sigint inherit_from ___ keeptmp line_width locking log_line_width _ log_timestamp mailcompress mailmethod mailport mailserver mailto mail_reports make makeflags mean_anyway minimize_rundirs minimize_builddirs no_monitor no_input_handler notes_wrap_indent output_root preenv section_specifier_fatal sendmail src.alt strict_rundir_verify sysinfo_program teeout version_url

III. Config file options for specmake

CC, CXX, FC
CLD, CXXLD, FLD
ONESTEP
OPTIMIZE, COPTIMIZE, CXXOPTIMIZE, FOPTIMIZE
PORTABILITY, CPORTABILITY, CXXPORTABILITY, FPORTABILITY...
RM_SOURCES

IV. Config file options for the shell

_ bench_post_setup _ ______ post_setup monitor_pre_bench monitor_post_bench monitor_wrapper monitor_specrun_wrapper submit

V. Config file options for the output report

A. Field scoping

B. Continued versus fixed-format fields

C. Free-form notes

D. Links in notes sections

E. Attachments

F. Test description

hw_avail license_num notes_test prepared_by sw_avail system_class system_name system_vendor tester test_sponsor

G. Benchmark description

notes_base notes_comp notes_peak notes_port sw_base_ptrsize sw_c_compiler sw_cxx_compiler sw_f_compiler sw_mpi_library sw_mpi_other sw_notes sw_other sw_peak_ptrsize

H. Component attributes

I. Node description(s)

node_tag_label node_tag_order node_tag_count node_tag_hw_vendor node_tag_hw__model node_tag_purpose node_tag_hw_cpu_name node_tag_hw_ncores node_tag_hw_ncoresorder node_tag_hw_ncoresperchip node_tag_hw_nchips node_tag_hw_nthreadspercore node_tag_hw_cpu_char node_tag_hw_cpu_mhz node_tag_hw_fpu node_tag_hw_pcache node_tag_hw_scache node_tag_hw_tcache node_tag_hw_ocache node_tag_hw_memory node_tag_sw_os node_tag_sw_state node_tag_hw_disk node_tag_sw_local_file node_tag_sw_shared_file node_tag_sw_other node_tag_hw_other node_tag_notes

J. Adaptor description(s)

node_tag1_hw_adaptor_tag2_model node_tag1_hw_adaptor_tag2_slot_type node_tag1_hw_adaptor_tag2_data_rate node_tag1_hw_adaptor_tag2_count node_tag1_hw_adaptor_tag2_ports_used node_tag1_hw_adaptor_tag2_driver node_tag1_hw_adaptor_tag2_firmware

K. Interconnect description(s)

interconnect_tag_hw_purpose interconnect_tag_hw_model interconnect_tag_hw_notes interconnect_tag_hw_switch interconnect_tag_hw_switch_count interconnect_tag_hw_switch_ports interconnect_tag_hw_switch_data_rate interconnect_tag_hw_switch_firmware interconnect_tag_hw_topo interconnect_tag_hw_vendor interconnect_tag_label interconnect_tag_order

VI. Deprecated options

A. SPEC/CPU rate runs

B. Feedack-directed optimization

C. Old-style descriptive formats

D. Obsolete hardware designs

E. Automatic thread-level parallelization

VII. The config file preprocessor

A. Defining macros

B. Un-doing macro definition

C. Using macros

D. Conditionals

1.%ifdef .. %endif

2.%ifndef .. %endif

3.%if .. %endif

4.%else

5.%elif

E. Informational directives

1.%warning

2.%error

VIII. Output files - and how they relate to your config file

A. Automatic backup of config files

B. The log file and verbosity levels

1. Search Strings

2. Temporary Debug Logs

3. Definitions of verbosity levels

C. Help, I've got too many logs

D. Finding the build directory

E. Files in the build directory

F. For more information

IX. About Alternate Sources

A. Example: Applying a src.alt

B. Developing a src.alt (brief introduction)

X. Troubleshooting

I. Introduction

I.A. What is a config file? (Background: benchmark philosophy.)

A config file contains:

• The instructions for building the benchmarks.
• The instructions for running the benchmarks.
• The description of the system under test.
• The key to result reproducibility.
• The guts, the real controls, the Good Stuff.
• The place where the benchmark philosophy hits the road.

A key decision that must be made by designers of a benchmark suite is whether to allow the benchmark source code to be changed when the suite is used.

If source code changes are allowed:

If source code changes are not allowed:

SPEC has chosen not to allow source code changes for the MPI2007 suite, except under very limited circumstances.

By restricting source code changes, SPEC separates the activity of porting benchmarks, which has a goal of being performance neutral, from the activity of using the benchmarks, where the goal is getting the best score possible. Prior to the first production use of MPI2007, SPEC invested substantial effort to port the suite to as many platforms as practical, including 32 and 64-bit systems; little-endian and big-endian hardware; Unix, Linux, and Microsoft Windows systems.

Are source code changes ever allowed? Normally, no. But if you discover a reason why you believe such a change is essential, SPEC wants to hear about it, and will consider such requests for a future revision of the suite. SPEC will normally not publish MPI2007 results using modified source code, unless such modifications are unavoidable for the target environment, are submitted to the SPEC HPG committee for review, are made available to all users of the suite, and are formally approved by a vote of the SPEC HPG committee.

So, if source code changes are not allowed, but the benchmarks must be compiled in a wide variety of environments, can the users at least write their own makefiles, and use -D options to select different environments? The answer to these two questions are "no", and "yes", respectively:

• No, you can't write your own makefiles.
• But yes, you can select portability options (such as -D).

You do this in the config file, which contains a centralized collection of all the portability options and optimization options for all the benchmarks in the MPI2007 suite. The SPEC tools then automatically generate the makefiles for you.

The config file contains places where you can specify the characteristics of both your compile time and run time environments. A general notation is used to express platform-specific conventions for compiling and running the benchmarks. It allows the advanced user to perform detailed manipulation of makefile options, but retains all the changes in one place so that they can be examined and reproduced.

The config file is one of the key ingredients in making results reproducible. For example, if a customer would like to run the MPI2007 suite on her own SuperHero Model 4 and discover how close results are in her environment to the environment used when the vendor published a MPI2007 result, she should be able to do that using only 3 ingredients:

1. The SPEC MPI2007 media, ordered from SPEC.
2. The software and hardware as specified in the full disclosure when the vendor published the original results.
3. The config file from the vendor's submission.

I.B. What does a config file affect?

A config file contains options targetting five distinct consumers:

1. The runspec tool, which provides overall control of the test,
2. The tool that compiles benchmarks: specmake,
3. Your shell, which is used for certain operations such as submiting to specific processors,
4. Readers of the results, and
5. The config file preprocessor.

To understand how to write a config file effectively, you need to understand which consumer you are addressing at any given point.

The above point seems worth emphasizing:

To understand how to write a config file effectively, you need to understand which consumer you are addressing at any given point.

This section gives you an overview of the consumers; more detail is included in later sections.

I.B.1. runspec

Various aspects of the operation of runspec can be affected by setting options within a config file. You'll find a list of these options in the table of contents for section II - including some that are available both on the runspec command line and some that can only be set within a config file.

For example, if michael.cfg includes the lines:

   output_format = text,ps
   tune          = base
   reportable    = 1
   runlist       = medium

then the defaults for the runspec command would change as specified. A user who types either of the following two commands would get precisely the same effect:

   runspec --config=michael
   runspec --config=michael --output=text,ps --tune=base --reportable medium

I.B.2. specmake

The tool specmake is simply GNU make renamed to avoid any possible conflicts with other versions of make that may be on your system. The options commonly used for specmake are listed in the table of contents for section III.

For example, these config file lines:

   CC           = cc
   CPORTABILITY = -DSPEC_SINGLE_UNDERSCORE
   OPTIMIZE     = -O4

are written to the makefile set that is ultimately used to build the benchmark, and are interpreted by specmake.

I.B.3. The shell

Some config file lines define commands that are handed off to the shell or, on Windows, the command interpreter. The list of these is in the table of contents for section IV.

For example, consider a config file that contains:

submit = let "MP_PROCS=$ranks"; poe $command

When using this config file, runspec will pass the above command to the shell to run the corresponding benchmark binary. It is the shell that actually carries out the requested commands, not runspec, so the syntax of the command depends on whether you are using the Unix shell (/bin/sh) or the Windows command interpreter (cmd.exe).

Because runspec can cause arbitrary commands to be executed,
it is therefore important to read a config file you are given before using it.

I.B.4. Readers of the results

If a SPEC MPI2007 result is published (for example, at http://www.spec.org/), it is expected to contain all the information needed for a reader to understand exactly what was tested. Fields that are informative for readers are listed in the table of contents for section V.

For example, config file lines such as these are addressed to the human reader:

   test_date = Nov-2008
   hw_avail  = Apr-2008
   sw_avail  = May-2008
   node_notes_015  = Note: Node 0 is used as the file server for the cluster.

In addition, for results published by SPEC, the config file itself is available to readers at http://www.spec.org/mpi2007/. The config file is presented as you wrote it, with three exceptions (protected comments, the MD5 section, and rawfile corrections for reader fields). The config file is made available because it is so important to reproducing results, as described in the Introduction. The config file is saved on every run, as a compressed portion of the rawfile, and can be accessed with runspec --rawformat --output_format=config <rawfile>.

I.B.5. The config file preprocessor

There is also a config file preprocessor, which is addressed via lines that begin with % in the first column. The config file preprocessor is a new SPEC tool, introduced with CPU2006 and MPI2007.

I.C. Config file structure

A config file contains:

• A header section.
• An arbitrary number of user-defined named sections, delimited by section markers.
• An automatically-generated MD5 section.

About scope: Every line of the config file is considered to be within the scope of one of the above three. Lines prior to the first section marker are in the scope of the header section. All other lines are either in the scope of the most recently preceding user-defined section marker, or else in the MD5 section.

A line within the scope of a named section may be overridden by a line within the scope of a different named section, according to rules that are described below.

I.C.1. Comments and whitespace

A comment begins with a #, and can be placed anywhere in a config file, either as a trailing end-of-line comment or as a whole line:

#
#   Header comment
#
output_format   = rsf,text,html,csv      # End-of-line comment.

   #> I didn't use the C++ beta version because of Bob's big back-end bug.

Blank lines can be placed anywhere in a config file.

Trailing spaces and tabs are stripped, unless they are preceeded by a backslash:

   CC_PATH=/path/with/no/trailing/spaces

That is turned into "/path/with/no/trailing/spaces". To preserve those trailing spaces, you'd simply add a backslash:

      CC_PATH=/path/with/trailing/spaces\ 

That is turned into "/path/with/trailing/spaces ".

Spaces within a line are usually ignored. Of course, you wouldn't want to spell OPTIMIZE as OPT I MIZE, but you are perfectly welcome to do either of the following:

   OPTIMIZE=-O2
   OPTIMIZE   =  -02

One place where spaces are considered significant is in notes, where the tools assume you are trying to line up your comments in the full disclosure reports. (Notes are printed in a fixed-width font.)

Spaces at the beginning of lines are ignored, except when attempting to address the preprocessor. Preprocessor directives always begin with a percent sign (%) in the first column. You can put spaces after the percent sign, if you wish, as shown by the examples below.

I.C.2. Header section

The header section is simply the first section, prior to the first occurence of a named section.

Most attempts to address runspec itself must be done in the header section. For example, if you want to set reportable=1, you must do so before any occurrences of section markers.

I.C.3. Named Sections

A named section is a portion of the config file that begins with a section marker and continues until the next section marker or the MD5 section is reached. The contents of the named section are applied based upon the precedence rules described in the following sections.

A "section marker" is a four-part string of the form:

   benchmark[,benchmark]*=tuning[,tuning]*=extension[,extension]*=machine[,machine]*:

These are referred to below as the 4 "section specifiers". The allowed values for the section specifiers are:

[*] The "machine" specifier works similarly to the extension specifier, but it does not affect the name of the executable produced, which, in many environments, makes it less useful than the extension specifier. This document does not describe the usage of the "machine" specifier, other than to note that it exists; if you feel particularly courageous, you can experiment with it.

But please be aware that if you use a single config file to build with two different machine settings, you will likely overwrite the original binaries on the second build, since the machine specifier does not affect the name of the generated executable.

Lists may be used in any of the slots in the section marker:

       104.milc,122.tachyon = base,peak = optLevel1,optLevel2 = arch1,arch2:

This capability is new with the MPI2007 and CPU2006 tool sets.

Trailing default section specifiers may be omitted from a section marker. Thus all three of these section markers are equivalent:

   104.milc=base=default=default:
   104.milc=base=default:
   104.milc=base:

Section markers can be entered in any order. Section markers can be repeated; material from identical section markers will automatically be consolidated. That is, you are welcome to start one section, start a different one, then go back and add more material to the first section. But please note that since there is no marker for the header section, you cannot go back to it.

By constructing section markers, you specify how you would like your options applied, with powerful defaulting and overriding capabilities. The next several sections walk through examples to demonstrate precedence, including how sections interact with each other.

I.C.3.a. Precedence of the benchmark specifier

For the benchmark specifier, the precedence is:

  highest   named benchmark
            suite or bset name
  lowest    default

Using default as the benchmark specifier

For example, consider this config file that only mentions default for the benchmark specifier:

   $ cat tmp.cfg
   runlist        = lammps
   size           = mtest
   iterations     = 1
   tune           = base
   output_format  = text
   teeout         = 1
   ranks          = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   $ runspec --config=tmp | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O3 -q64 lammps.cpp
   $ 

The config file above is designed for quick, simple testing: it runs only one benchmark, namely 126.lammps, using the smallest (mtest) workload, runs it only once, uses only base tuning, outputs only the text-format (ASCII) report, and displays the build commands to the screen (teeout). To use it, we issue a runspec command, and pipe the output to grep to search for the actual generated compile command. (Alternatively, on Windows, we could use findstr on the generated log file).

The careful reader may ask, "Why does the runlist reference lammps rather than 126.lammps?" The answer is that the runlist can use benchmark numbers or any abbreviation that is sufficient for uniqueness; any of the following would have the same effect: 126.lammps, 126, or lammps. This is the same rule as for the corresponding option on the command line.

The results show that the tuning applied was the expected -O3 (which mean optimization level 3, for the IBM mpCC compiler). The tools have automatically added -c -o lammps.o to specify where the object file is to be written. The switch -DFFT_NONE was also added automatically.

Using a bset list as the benchmark specifier

The next example differs from the previous one by adding a section marker with medium_all_cpp, for the C++ benchmarks, as the first section specifier:

   $  cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   medium_all_cpp=default=default=default:
   OPTIMIZE = -O4

   $ runspec --config=tmp | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O4 -q64 lammps.cpp
   $

The second OPTIMIZE line is used above because the reference to the C++ benchmarks is considered to be more specific than the overall default.

Using a named suite as the benchmark specifier

A named suite is one case of a bset, with the property that it contains all the benchmarks necessary for a reportable run. The example below uses the medium section marker as the first section specifier, to denote the entire medium sized data suite:

   $  cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   medium=default=default=default:
   OPTIMIZE = -O4

   $ runspec --config=tmp | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O4 -q64 lammps.cpp
   $

The second OPTIMIZE line is used above because the reference to the medium suite is considered to be more specific than the overall default.

Using a named benchmark as the benchmark specifier

Furthermore, we can add a specifier that mentions lammps by name:

   $  cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   medium_all_cpp=default=default=default:
   OPTIMIZE = -O4

   126.lammps=default=default=default:
   OPTIMIZE = -O5 -qstrict

   $ runspec --config=tmp | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
   $

The third OPTIMIZE line wins above, because it is included in the section that is considered to be the most specific.

Order of differing sections does not matter:

But what if we had said these in a different order?

   $ cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   126.lammps=default=default=default:
   OPTIMIZE = -O5 -qstrict

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   medium_all_cpp=default=default=default:
   OPTIMIZE = -O4

   $ runspec --config=tmp | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp

Notice above that the order of entry is not significant; it's the order of precedence from least specific to most specific.

Order of the same section does matter:

When a specifier is listed more than once at the same descriptive level, the last instance of the specifier is used. Consider this case:

   126.lammps=default=default=default:
   OPTIMIZE = -O4

   122.tachyon=default:
   OPTIMIZE = -O5

   126.lammps=default=default=default:
   OPTIMIZE = -O3

The ending value of OPTIMIZE for 126.lammps is -O3, not -O4.

I.C.3.b. Precedence of the tuning specifier

For the tuning specifier, either base or peak has higher precedence than default.

Here is an example of its use:

   $ cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base,peak
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   default=base=default=default:
   OPTIMIZE       = -O4

   default=peak=default=default:
   OPTIMIZE       = -O5 -qstrict

   $ runspec --config=tmp -T base | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O4 -q64 lammps.cpp
   $ runspec --config=tmp -T peak | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
   $ 

In the above example, we compile 126.lammps twice: once for base tuning, and once for peak. Notice that in both cases the optimizations defined by the more specific section markers have been applied, namely -O4 and -O5 -qstrict, rather than -O3 from default=default=default=default.

I.C.3.c. Precedence of the extension specifier

For the extension specifier, any named extension is at a higher precedence level than the default.

Using an extension found in the config file

Analogous to the example above, the choice of extension specifier determines the level of optimization that is applied:

   $ cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64
   submit         = poe $command -procs $ranks

   default=base=myke=default:
   OPTIMIZE       = -O4

   default=base=yusuf=default:
   OPTIMIZE       = -O5 -qstrict

   $ runspec --config=tmp --extension=myke | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O4 -q64 lammps.cpp
   $
   $ runspec --config=tmp --extension=yusuf | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
   $ 
   $ cd $SPEC/benchspec/MPI2007/126.lammps/exe
   $ ls -lt | head -3
   total 9344
   -rwxrwxr-x   1 spec     staff       2330870 Jun 13 09:50 lammps_base.yusuf
   -rwxrwxr-x   1 spec     staff       2446066 Jun 13 09:34 lammps_base.myke
   $

Notice above that two different versions of 126.lammps were built from the same config file, and the default OPTIMIZE setting was overridden the extension rule in each case. Both executables are present in the exe directory for 126.lammps.

Using an extension that is not found in the config file

The previous section demonstrated use of the runspec switch --extension to select among extensions defined in the config file. But what if the extension on the command line is not mentioned in the config file? The example below continues immediately from the example just above:

   $ runspec --config=tmp --extension=yusoff
   runspec v4200 - Copyright 1999-2007 Standard Performance Evaluation Corporation
   ...
   ERROR: The extension 'yusoff' defines no settings in the config file!
          If this is okay and you'd like to use the extension to just change
          the extension applied to executables, please put
       allow_extension_override = yes
          into the header section of your config file.

By default, if you mention an extension on the runspec command line that does not exist in the config file, the tools refuse to build.

Extension override

But if you add allow_extension_override=yes to the top of the config file, then the tools will build or run with the extension you specified, using the same settings as they would have used if no extension had been entered on the runspec command line.

The next example continues with a config file that adds allow_extension_override to the previous example config file:

   $ diff tmp.cfg tmp2.cfg
   0a1
   > allow_extension_override=yes
   $
   $ runspec --config=tmp2 --extension=yusoff | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O3 -q64 lammps.cpp
   $
   $ cd $SPEC/benchspec/MPI2007/126.lammps/exe
   $ ls -lt | head -2
   total 12472
   -rwxrwxr-x   1 spec     staff       1599589 Jun 13 10:02 lammps_base.yusoff

Notice above that although the tools now consent to build with the requested extension, the library settings now falls back to the default, since yusoff does not match any section markers.

(For CPU2000/OMP2001/HPC2002, the tools silently accepted any extension, including typos, which sometimes led to surprising results. MPI2007 tries to reduce surprises by rejecting your typos, unless you set allow_extension_override.)

I.C.3.d. Combining specifier types

If more than one section applies to a particular benchmark without disagreement among them, then all are applied.

Consider this example:

   $ cat tmp.cfg
   runlist       = lammps
   size          = mtest
   iterations    = 1
   tune          = base
   output_format = text
   teeout        = 1
   ranks         = 32

   default=default=default=default:
   CXX            = mpCC_r
   OPTIMIZE       = -O3

   126.lammps=default=default=default:
   submit         = poe $command -procs $ranks

   default=peak=default=default:
   OPTIMIZE       = -O5 -qstrict

   default=default=AIX64=default:
   EXTRA_LDFLAGS  = -q64
   EXTRA_CXXFLAGS = -q64

   $ runspec --config=tmp --tune=peak --ext=AIX64 | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
   $ 

Notice above that all three sections applied: the section specifier for 126.lammps, the specifier for peak tuning, and the specifier for extension AIX64.

I.C.3.e. Precedence among section types

If sections conflict with each other, the order of precedence is:

     highest     benchmark
                 suite or bset
                 tuning
                 extension
     lowest      machine

And this order can be demonstrated as follows:

    $  cat tmp.cfg
     runlist       = lammps
     size          = mtest
     iterations    = 1
     tune          = base
     output_format = text
     teeout        = 1
     makeflags     = -j30
     ranks         = 32
  
     default=default=default=default:
     CXX            = mpCC_r
     CC             = mpcc_r
     FC             = mpxlf95_r
     OPTIMIZE       = -O3
     EXTRA_LDFLAGS  = -q64
     EXTRA_CXXFLAGS = -q64
     EXTRA_CFLAGS   = -q64
     submit         = poe $command -procs $ranks
  
     medium_all_c=default=default=default:
     OPTIMIZE       = -O4
  
     126.lammps=default=default=default:
     OPTIMIZE       = -O5 -qstrict
  
     default=peak=default=default:
     OPTIMIZE       = -O5
  
     default=default=AIX64=default:
     OPTIMIZE       = -O
     $
     $ runspec --config=tmp lammps | grep lammps.cpp  
[1]  mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
     $ runspec --config=tmp --tune=peak lammps | grep lammps.cpp
[2]  mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
     $ runspec --config=tmp --extension=AIX64 lammps | grep lammps.cpp
[3]  mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O5 -qstrict -q64 lammps.cpp
     $ 
     $ runspec --config=tmp --tune=base tachyon | grep main.c
[4]  mpcc_r -c -o main.o -DSPEC_MPI -DNDEBUG -O4 -q64 main.c
     $ runspec --config=tmp --tune=peak tachyon | grep main.c
[5]  mpcc_r -c -o main.o -DSPEC_MPI -DNDEBUG -O4 -q64 main.c
     $ runspec --config=tmp --extension=AIX64 tachyon | grep main.c
[6]  mpcc_r -c -o main.o -DSPEC_MPI -DNDEBUG -O4 -q64 main.c
     $
     $ runspec --config=tmp --tune=base GemsFDTD | grep GemsFDTD_MPI.fppized.o
[7]  mpxlf95_r -c -o GemsFDTD_MPI.fppized.o -O3 -q64 GemsFDTD_MPI.fppized.f90
     $ runspec --config=tmp --tune=peak GemsFDTD | grep GemsFDTD_MPI.fppized.o
[8]  mpxlf95_r -c -o GemsFDTD_MPI.fppized.o -O5 -q64 GemsFDTD_MPI.fppized.f90
     $ runspec --config=tmp --extension=AIX64 GemsFDTD | grep GemsFDTD_MPI.fppized.o
[9]  mpxlf95_r -c -o GemsFDTD_MPI.fppized.o -O -q64 GemsFDTD_MPI.fppized.f90
     $ runspec --config=tmp --tune=peak --extension=AIX64 GemsFDTD | grep GemsFDTD_MPI.fppized.o
[10] mpxlf95_r -c -o GemsFDTD_MPI.fppized.o -O5 -q64 GemsFDTD_MPI.fppized.f90
     $ 

Notice above that the named benchmark always wins: lines [1], [2], and [3]. If there is no section specifier that names a benchmark, but there is a section specifier that names a suite or bset, then the suite or bset wins: lines [4], [5], and [6]. If there are no applicable benchmark or suite specifiers, then tuning or extension can be applied: lines [8] and [9]. But if both tuning and extension are applied, tuning wins [10].

I.C.4. MD5 Section

The final section of your config file is generated automatically by the tools when the benchmarks are compiled, and looks something like this:

   __MD5__
   126.lammps=base=none=default:
   # Last updated Thu May 11 08:53:12 2007
   optmd5=a0104c0975ee3b341e73437843df57a9
   baggage=
   compile_options=\
   @eNpz9vcNsFJITlbQBaJ8hfyCksz8vGK9fAVdl+AAV+d454BQINPPxdUp1F1BQUG3wt9YQbdcAR3Y\
   FOeXFiWn2nE5Wyk4O9sqJScrgZn+Tl7+ASG2SiimK3EBrQQa7Obj6B4MlMO0SYnL30oBqNHT1zPK\
   FagCYqsSl4+nnzfYtVgcYpOflJWaXFJshySGsBPkGh8XiMOwmw1W4B8KciySSwGYpEmr
   exemd5=9b42a21f12b1fbb4e87cd9bacd781c43

The "MD5" is a checksum that ensures that the binaries referenced in the config file are in fact built using the options described therein. For example, if you edit the config file to change the optimization level for 126.lammps, the next time the file is used for lammps, the tools will notice the change and will recompile it.

You can optionally disable this behavior, but doing so is strongly discouraged. Not only is the result not reportable, but the binaries you run may not be compiled under the conditions you think they are compiled under. See the acerbic remarks in the description of check_md5, below.

If you would like to see what portions of your config file are used in computing the MD5 hash, runspec with --debug=30 or higher, and examine the log file.

For published results, the published config file (from rawformat --output_format=config) does not include the MD5 section.

I.C.5. Shell-like "here documents" and continued lines

Shell-style "here documents" are supported for setting variables to multi-line values. Continued lines (with \) are also supported:

   $ cat tmp2.cfg
   expand_notes  = 1
   size          = mtest
   runlist       = lammps
   iterations    = 1
   output_format = text

   foo =<<EOT

   This +
   is a +
   test +
   EOT

   bar = \
         and +\
         so  +\
         is  +\
         this+

   notes01 = $foo
   notes02 = $bar

   $ runspec --config=tmp2 | grep txt
           format: ASCII -> /ailuropoda/raj/spec/result/MPIM2007.159.mtest.txt
   $ grep + ../result/*159*txt
       This +
       is a +
       test +
             and +
             so  +
             is  +
             this+
   $

Note: although continued lines are supported, they are rarely used. The more common method of continuation is by appending a number to a field, as described in the section "Field scoping and continuation".

I.C.6. Included files

It is possible to include another file in your config file. A typical use for this feature might be to keep all the software information in the main config file, but to include the hardware information about the current System Under Test (SUT) in another file. For example:

   $ cat tmp.cfg
   output_format = text
   iterations    = 1
   size          = mtest
   sw_compiler   = myC V1.0
   sw_avail      = Mar-2007
   runlist       = lammps
   include: SUT.inc

   default=base:
   OPTIMIZE = -O
   $ cat SUT.inc
   hw_model = SuperHero IV
   hw_avail = Feb-2008

   $ runspec --config tmp | grep txt
           format: ASCII -> /manas/spec/result/MPI2007.160.mtest.txt
   $ grep avail ../result/*160.mtest.txt
    [...]       Hardware availability: Feb-2008
    [...]       Software availability: Mar-2007
   $ 

Notice above that the report mentions both the hardware and software dates.

I.D. Variable Substitution

I.D.1. By runspec, at startup: $[variable]

Substitution for variables of the form $[variable] happens immediately after the config file is read by runspec. Any value that's set in the config file and is visible in the scope where the variable is used can be substituted. Because of the named section scoping restriction, if you want to use variable substitution to note your optimization flags, the notes for the individual benchmarks must be in those benchmarks' sections:

122.tachyon=peak=default=default:
PEAKFLAG=-gofast
# The following will turn into what you expect
notes_peak_400_1=I use $[PEAKFLAG]

122.tachyon=base=default=default:
BASEFLAG=-besafe
# The following will turn into what you expect:
notes_base_400_1=I use $[BASEFLAG]
# The following will NOT WORK:
notes_base_400_2=My brother likes $[PEAKFLAG]

You can't substitute variables that don't exist or whose values aren't known when the config file is read.

Wrong:

ext = foo

default:
OPTIMIZE = -xO2
notes01 = my ext is $[ext]

default=default=bar:
OPTIMIZE = -xO1
notes02 = my ext is $[ext]

This doesn't work because the sorting of which extensions to use doesn't happen until after the config file is processed. In this particular example, it's obvious (to you) what the value should be, but the tools aren't as clever as you are.

Perhaps the most useful variable is the one for the top of the SPEC MPI2007 tree, $[top], often found in contexts such as:

    flagsurl = $[top]/myflagsdir/myflagsfile.xml

Variables of possible interest might include:

You can substitute with most options that you enter into the config file, including: action, allow_extension_override, backup_config, basepeak, check_md5, check_version, command_add_redirect, config, delay, deletework, difflines, env_vars, expand_notes, expid, ext, fake, flagsurl, http_proxy, http_timeout, ignore_errors, ignore_sigint, info_wrap_columns, iterations, line_width, locking, log_line_width, mach, mail_reports, mailcompress, mailmethod, mailport, mailserver, mailto, make, make_no_clobber, makeflags, mean_anyway, minimize_builddirs, minimize_rundirs, no_input_handler, no_monitor, notes_wrap_columns, notes_wrap_indent, output_format, output_root, rawformat, rebuild, reportable, runlist, section_specifier_fatal, sendmail, setprocgroup, size, strict_rundir_verify, sysinfo_program, table, teeout, tune, username, verbose, version_url.

You can also print out the value of additional variables that you may have created.

Here is a sample config file that illustrates square bracket variable substitution:

$ cat x.cfg
expand_notes = 1
runlist      = medium
action       = validate
myfriend     = jamiemeow
output_root  = /tmp
flagsurl     = $[top]/Docs/flags/flags-advanced.xml

notes01      = Today, I am running $[runlist] in $[top] on a $[OS] system 
notes02      = Today the flags file is $[flagsurl]
notes03      = Today, my favorite friend is $[myfriend]

$ runspec --config=x  --fakereportable | grep txt
        format: ASCII -> /tmp/result/MPI2007.002.txt
$ grep Today /tmp/result/MPI2007.002.txt
     Today, I am running medium in /spec/mpi2007 on a unix system 
     Today the flags file is /spec/mpi2007/Docs/flags/flags-advanced.xml
     Today, my favorite friend is jamiemeow

You can't use square brackets to substitute variables whose value changes during a run or build.

Wrong:

default=default=default=default:
#        I executed ''
notes0 = I executed '$[command]'

What did you expect?

Don't worry -- you'll receive a warning if you use a variable that the tools don't know about. It's up to you to heed them.

I.D.2 By runspec, during a run: $variable, ${variable}

The second round performed by runspec uses Perl variable interpolation. Only Perl scalars (denoted by a leading $) can be interpolated. For example, notes001 below uses the log file number (generated by the tools) and the hardware availability date (which was set directly):

$ cat tmp.cfg
runlist       = lu
tune          = base
size          = mtest

iterations    = 1
output_format = text

expand_notes  = 1
hw_avail      = May-2007
notes001      = This run is from log.$lognum with hw_avail $hw_avail

$ runspec -c tmp | grep txt
        format: ASCII -> /spec/david/result/MPIM2007.029.mtest.txt
$ grep with ../result/*029*txt
     This run is from log.029 with hw_avail May-2007
$ 

In this case, $hw_avail could also have been substituted in the first round by writing it as $[hw_avail]. In general, for variable interpolation, the earlier the better.

To put text immediately after a variable, you need to make it possible for the parser to see the variable that you want, by using braces:

   % tail -2 tmp.cfg
   notes001 =You have done ${lognum}x runs tonight, go to bed.

   % runspec -c tmp | grep txt
      format: ASCII -> /john/result/MPIM2007.103.mtest.txt
   % grep done /john/result/MPIM2007.103.mtest.txt
      You have done 103x runs tonight, go to bed.

Interpolation won't always do what you wish it might do: for example, some variables are only defined at certain times, and your submit or notes line might be interpolated at a different time. When debugging a config file that uses variable interpolation, you will probably find --size mtest useful.

Some things that you might choose to interpolate include:

Variable interpolation is most commonly used to paramaterize the MPI driver when a benchmark is invoked by the submit directive. In the two examples below, $command is replaced with the invocation of each benchmark, including the name of the executable and its parameters, and $ranks is replaced by the number of ranks that is to be used with that benchmark for the base or peak run:

submit = poe $command -procs=$ranks

or

env_vars     = 1
ENV_MP_PROCS = $ranks
submit = poe $command

If you'd like a complete list of the variables that you can use in your commands (relative to the config file you're using), set runspec's verbosity to 35 or higher (-v 35) and do a run that causes a command substitution to happen, with expand_notes=1.

I.D.3. By the shell: \$VARIABLE

Substitution by the shell - or by the windows command interpreter - uses backslash dollar sign. Because Perl variables look a lot like shell variables, you need to specially protect shell variables if you want to prevent Perl from trying to interpret them. Notice what happens with the protected and unprotected versions:

$ cat tmp.cfg
runlist              = mcf
size                 = mtest
tune                 = base,peak
iterations           = 1

output_format        = text 
teeout               = 1
expand_notes         = 1

default=peak=default=default:
submit = echo "home=$HOME; spec=$SPEC;" > /tmp/chan; $command

default=base=default=default:
submit = echo "home=\$HOME; spec=\$SPEC;" > /tmp/nui; $command
$ runspec --config=tmp > /dev/null
$ cat /tmp/chan
home=; spec=;
$ cat /tmp/nui
home=/home/chris; spec=/spec/mpi2007;
$ 

In the first submit command, $HOME and $SPEC were gobbled up by runspec. But since those are not the names of variables that can be interpolated, empty strings were the result. In the second command, the backslashes prevented runspec from interpreting the variables, so they were seen by the shell instead.

I.D.4. By specmake: $(VARIABLE)

Variables with a dollar sign and parentheses, aka "round brackets", are substituted by specmake. For example:

    COMPILER_DIR=/usr/local/bin/
    CC=$(COMPILER_DIR)cc

For a more extensive example of variable substitution handled by specmake, see the SPEC CPU2000 example at www.spec.org/cpu2000/docs/example-advanced.cfg. Search that file for LIBS, and note the long comment which provides a walk-through of a complex substitution handled by specmake. Note: a MPI2007 version of that example will be provided at a later date; but the concepts, from the CPU2000 example, are expected to work in a similar fashion for MPI2007.

Deprecated feature alert: Although it is also possible to pass information to specmake using curly brackets: ${SPECMAKE}, this is not recommended. Instead, you should consistently use curly brackets to address runspec and round brackets to address specmake. It is possible that a future version of runspec may insist on interpolating curly brackets itself, rather than allowing specmake to do so.

I.D.5. Example: controlling rank counts in the AIX MPI driver

Here is a simple but useful example of controlling the rank counts in the MPI benchmarks. First, the benchmarks are invoked using the form

	submit = poe $command

The poe is the MPI driver for the AIX operating system. The command is the variable containing the invocation of the benchmark executable with its parameters, and is assigned by runspec in the Perl variable interpolation phase. Given that the ranks count has been assigned on the command-line:

	runspec --ranks 32 ...

or at the top of the config-file:

	ranks = 32

here are several ways that the ranks can be specified to the poe driver:

[1]      submit = poe $command -procs $ranks           # Ranks are set by an explicit parameter to "poe".

[2]      env_vars = 1                                  # "poe" reads the ranks from the environment variable "MP_PROCS".
         ENV_MP_PROCS=$ranks
         submit = poe $command

[3]      submit = let "MP_PROCS=$ranks"; poe $command  # Here the environment variable is set in the shell-execution stage.

[4]      submit = let "COUNT=$ranks"; poe $command -procs \$COUNT   # Here assigned to an intermediate shell variable.

The first three cases rely strictly on variable interpolation. In case [4], the $ranks and $command are expanded in the variable-interpolation stage, while the $COUNT is not expanded because of its preceding '\'. The string that is passed to the shell has the form

	     COUNT=32; poe ... -procs $COUNT

where ... is the expansion of the $command parameter.

I.D.6. Limitations on variable substitution

Once runspec hands control over to specmake or to the shell, the results of further substitution are invisible to runspec. For this reason, you can't say:

Wrong:

MYDIR         = /usr/gretchen/compilers
FC            = $(MYDIR)/f90
notes_comp001 = compiler: $(FC)

However, there are a couple of ways to get around this restriction. The best way for global settings is to use the preprocessor:

%define MYDIR /usr/gretchen/compilers
FC            = %{MYDIR}/f90
notes_comp001 = compiler: %{MYDIR}/f90

That leaves a little to be desired, though, doesn't it? If your Fortran compiler is changed to 'f2001', you still need to remember to change it in two places. You could of course define a whole macro for this:

%define MYFC /usr/gretchen/compilers/f90
FC            = %{MYFC}
notes_comp001 = compiler: %{MYFC}

But what if you have a config file where FC might be set in multiple places, and you really want to know how it was set right here? In that case, use a combination of the preprocessor and variable substitution:

$ cat right_here.cfg 
%define MYDIR /usr/gretchen/compilers

default=base:
FC            = %{MYDIR}/f2001
notes_comp001  = For base, we used this Fortran: $[FC] 

127.wrf2=peak:
FC            = %{MYDIR}/f77
notes_comp002 = For 127.wrf2 peak, we used this Fortran: $[FC]

$ runspec -c right_here.cfg --fakereportable fp | grep txt       
        format: ASCII -> /usr/gretchen/spec/result/MPI2007.179.txt
$ tail -15 ../result/*179.txt

                          Compiler Invocation Notes
                          -------------------------
     For base, we used this Fortran: /usr/gretchen/compilers/f2001 
     For 127.wrf2 peak, we used this Fortran: /usr/gretchen/compilers/f77

    SPEC and SPECfp are registered trademarks of the Standard Performance
    Evaluation Corporation.  All other brand and product names appearing
    in this result are trademarks or registered trademarks of their
    respective holders.
-----------------------------------------------------------------------------
For questions about this result, please contact the tester.
For other inquiries, please contact [email protected].
Copyright 2007 Standard Performance Evaluation Corporation
Generated on Wed Aug  2 09:39:53 2007 by SPEC MPI2007 ASCII formatter v4626
$ 

I.D.7. Unsetting a variable with %undef%

It is sometimes useful to be able to undo the setting of a variable that is defined in a lower-precedence section. This is easily accomplished using the special value %undef%:

  $ cat gnana.cfg
   teeout = yes
   action = build
   runlist = lammps

   default=default:
   OPTIMIZE  = -O3
   COPTIMIZE = -O5

   126.lammps=peak:
   COPTIMIZE = %undef%

   $ runspec --config=gnana --tune=base | grep lammps.cpp
   c++ -c -o lammps.o -DFFT_NONE -O3 -O5 lammps.cpp
   $ runspec --config=gnana --tune=peak | grep lammps.cpp
   c++ -c -o lammps.o -DFFT_NONE -O3 lammps.cpp
   $ go lammps
   /spec/gnana/kit91/benchspec/MPI2007/126.lammps
   $ cd run/build_peak_none.0000/
   $ grep OPT Make*
   Makefile.spec:COPTIMIZE        = 
   Makefile.spec:OPTIMIZE         = -O3

As you can see in the peak compilation, the -fast flag was not present because the setting for COPTIMIZE had been deleted.

II. Config file options for runspec

This section documents options that control the operation of runspec itself.

II.A. Options that can also be used on the runspec command line

The following items can be specified in a config file, and have the same meaning as if they are specified on the runspec command line. Please see runspec.html for details.

In general, if options can be specified on both the runspec command line and in a config file, the command line will win vs. items specified in the header section, but will not win over items specified in named sections. Effectively, the order of precedence is:

   named sections (highest)
   command line
   header section (lowest)

In the table that follows, the "Use In" column indicates where the option can be used:

SPEC MPI2007 V1.1 note: if you select basepeak=1 for a benchmark, the number of ranks in peak will be forced to be the same as in base. In SPEC MPI2007 V1.0, selection of the number of ranks could differ, but this was deemed to be an error. If you want to run the same tuning in both base and peak, while changing the number of ranks, you will need to build two binaries with the same compiler switches.

   http_proxy     = http://webcache.tom.spokewrenchdad.com:8080 

II.B. Options for runspec that can only be used in a config file

The following options control the operation of runspec, but can not be specified on the command line. Instead, they must be specified in the config file.

In the table that follows, the "Use In" column indicates where the option can be used:

Note that requesting a parallel build with makeflags = -j N causes multiple processors to be used at build time. It has no effect on how multiple processors are used at run time, and so does not affect how you report on parallelism.

benchspec/CPU2006/nnn.benchmark/build/build... (Unix) or
benchspec\CPU2006\nnn.benchmark\build\build... (Windows)

benchspec/CPU2006/nnn.benchmark/run/build... (Unix)
benchspec\CPU2006\nnn.benchmark\run\build... (Windows)

   $ ls -l bwaves_base.tmp3
   -rwxrwxr-x   1 david ptg       304964 May 16 10:16 bwaves_base.tmp3
   $ ldd bwaves_base.tmp3 | head -3
           libmvec.so.1 =>  /lib/libmvec.so.1
           libfui.so.2 =>   (file not found)
           libfai.so.3 =>   (file not found)
   $ 

   check_md5=0
   env_vars=1
   410.bwaves:
   ENV_LD_LIBRARY_PATH=/spec/david/lovecraft/lib

122.tachyon=default:
#> I am posting this config file for use by others in the
#> company, but am forcing it to fail here because
#> I want to force users to review this section.
#>
#> Once you find your way here, you should test whether
#> bug report 234567 has been fixed, by using the first
#> line below.  If it has not been fixed, then use the
#> second.  In either case, you'll need to remove the
#> fail_build.
#>
#>   - Pney Guvaxre
#>     Boomtime, the 66th day of Confusion in the YOLD 3172

# OPTIMIZE = -Osuperduper
# OPTIMIZE = -Omiddling
fail_build = 1

   $ cat -n tmp8.cfg
        1  iterations = 1
        2  size       = mtest
        3  teeout     = yes
        4
        5  default=default:
        6  OPTIMIZE = -O1 
        7
        8  medium_all_c,medium_all_cpp=default:
        9  OPTIMIZE = -O2
       10
       11  122.tachyon=default:
       12  OPTIMIZE = -O3 
       13  CC = mpcc_r
       41
       15  126.lammps=peak:
       16  inherit_from = 122.tachyon:default:default:default
       17  CXX = mpCC_r
   $ runspec --config tmp8 --tune base lammps | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O2 lammps.cpp
   $ runspec --config tmp8 --tune peak tachyon | grep lammps.cpp
   mpCC_r -c -o lammps.o -DSPEC_MPI -DNDEBUG -DFFT_NONE -O3 lammps.cpp
   

   [email protected]
   output_format=text,mail

   [email protected]
   output_format=text,mail
   mail_reports=text

III. Config file options for specmake

Most commonly used variables:

Other build variables:

User-defined variables:

You can also make up your own variable names, which specmake will use (and perform substitution on). A good example of this is for managing compilers that are located under different paths:

C_COMPILER =
F_COMPILER =
#C_COMPILER = /c/dev_050810/vacpp
#F_COMPILER = /c/dev_050810/xlf

CC   = ${C_COMPILER}/usr/bin/mpcc_r
FC   = ${F_COMPILER}/usr/bin/mpxlf95_r

The CC and FC compilers will be found at the paths determined by the C_COMPILER and F_COMPILER variables. As stated, the example above uses the default paths under /usr/bin/. To use the alternate paths under /c/dev_050810/vacpp/usr/bin/ and /c/dev_050810/xlf/usr/bin/, uncomment the second set of assignment lines prior to invoking runspec.

Assigned variables:

A long list of variables are defined and set in the benchspec/Makefile.defaults file, the individual benchspec/MPI2007/*/Spec/object.pm files, and the SPEC tools. Setting these variables in your config-file is not supported and is unlikely to accomplish your desired goal. The settings of these variables are only interesting some technical cases, for example:

• You may find that your compiler and linker are being passed incompatible parameters, and need to work backwards from the variable assignments to understand how to arrange the settings of the original config-file variables.
• A profiling script requires information on the benchmark, such as the executable name or source language, and you pass the variable values as explicit parameters to the script.

Here is the list of variables, and where their values are set:

About Automatic Rebuilds

Since the release of SPEC CPU2000, the SPEC CPU, OMP and HPC toolsets have attempted to keep config files and binaries in synch with each other (unless you have set check_md5=0, which is not recommended). This generally means that edits to your config file have often resulted in the binaries being rebuilt, sometimes to the dismay of testers who found that rebuilds were attempted at inconvenient times. The inconvenience was compounded by the fact that the first step in a rebuild is to delete the old binary, so even a very fast interrupt of the run wouldn't help: once the rebuild would start, your binary was gone.

New with CPU2006 and MPI2007 V1.1, unexpected rebuilds have been reduced.

In SPEC MPI2007 V1.0, the tools were much more likely to trigger a rebuild of the benchmark binaries than they are in V1.1, because unrecognized options (e.g. a mis-spelled CXXOPTIMZIE, or a user-defined option such as MY_OPTS) would be passed to specmake, and the tools had no way to know what specmake did with such options. Now, the tools record only the options actually used by specmake, plus the options that are sent to the shell (e.g. via submit), described in the next section). With this more careful recording, config file changes are less likely to trigger rebuilds, unless they actually affect the generated binary.

The tools do not promise to entirely eliminate unexpected rebuilds. Occasionally, they may make assumptions that seem conservative about config file options that might affect the generated binary.

Testing option sensitivity: If you would like to test whether a config file option change might cause a rebuild, without actually DOING the rebuild, here is a recommended procedure:

1. copy the config file to a test version (let's call it: mytest.cfg)
2. make the edits in the mytest.cfg
3. make sure that mytest.cfg does NOT change the default for check_md5
4. enter this command: runspec --config mytest --size mtest --iterations 1 --noignore_errors --nobuild ...

In the above command:

• The --size mtest runs the short workload, so the run will complete quickly.
• We run only one iteration.
• Saying --noignore_errors will cause an exit on the first error.
• And, most importantly, the --nobuild prevents a rebuild. Using this option will cause the tools to complain and exit if they think the binary is out of date, but they will not attempt to actually do the rebuild, and, in particular, your existing binary will not be deleted.

IV. Config file options for the shell

Some directives in your config file cause commands to be executed by your shell (/bin/sh) or by the Windows command interpreter (cmd.exe). The most essential case is

Because runspec can cause arbitrary commands to be executed,
it is therefore important to read a config file you are given before using it.

In addition to this are directives that can invoke performance measurement tools before and after each benchmark is set up or invoked:

A good example of the monitor_pre_bench / monitor_post_bench is to read a counter register before a benchmark is run and again after it finishes, or to start tracing before the benchmark runs and to stop traces after it finishes:

monitor_pre_bench  = trcon          # Trace OS events into a file.
submit             = ...
monitor_post_bench = trcoff         # Stop tracing.

As an alternative to using these directives, the submit form can be used to invoke a script, which in turn runs the performance measurement tool in conjuction with the benchmark $command. The result of the $command must be returned as the stdout of the wrapper. Using such a wrapper may not be acceptable in a submittable run, since the benchmark invocation can not be inferred from the config file. On the other hand, the monitor conventions may not work:

monitor_pre_bench  = vmstat $interval 1>>$report 2>>$logfile &; PID=$!		# Start monitor in background and record the Process ID.
submit             = ...
monitor_post_bench = kill $PID												# Kill the monitor process.

The problem is that we can derive the PID of the performance monitor at the point we invoke it, but have no easy way to capture it and pass it to the kill command after the benchmark finishes running. This may not be an issue with some monitoring tools, but in complex cases it is better to wrap both the monitor management and benchmark invocation into a single submit script which is passed $command as a parameter:

vmstat $interval 1>>$report 2>>$logfile &
PID=$!

$*                                                      # Run the program.

kill $PID

Directives that can assist in this are:

V. Config file options for the output report

The result of a SPEC MPI2007 run is a human-readable report that is generated in various formats. Whether or not you submit your result to SPEC, the report should be in a consistent format and should correctly describe the system and the conditions under which the measurement was made. The report is broken into the following sections:

1. Measurement results
2. System summary description
3. Benchmark description
4. Node description(s)
5. Interconnect description(s)

Each section consists of a formatted table of information followed by a free-form notes section. The config-file includes a set of fields that specify the contents of each section, other than fields that are generated by the run, such as the measurement results and date. These fields and the conventions for assigning them are described in the following sections.

V.A. Field scoping

Note that the descriptive fields are scoped by config-file section markers - that is, you can vary them according to the type of run that you are doing. For example:

   medium_all_c,medium_all_mixed=default=default=default:
   sw_compiler1 = Compaq C X6.2-259-449AT 
   CC           = cc -v      

   medium_all_cpp=default=default=default:  
   sw_compiler2 = DIGITAL C++ V6.1-029-408B6
   CXX          = cxx -v

   medium_all_fortran,medium_all_mixed=default=default=default:
   sw_compiler3 = KAP Fortran V4.2
   FC           = kf90 -v

In the above example, the information about the C, C++, or Fortran compilers will be printed if you run a benchmark that is written (or partly written) in that language. For example, if you only run 126.lammps, only the DIGITAL C++ V6.1-029-408B6 will appear in the report. Note that a reportable run of medium includes all the benchmarks, so all the compiler details will be printed.

V.B. Continued versus fixed-format fields

In several cases a field is used to describe complex information and can be continued to span multiple lines. The above example uses the forms

	sw_compiler  = 
	sw_compiler1 =
	sw_compiler2 =
	sw_compiler3 =

to generate a 2-to-3-line compiler description in the output report. Fields which allow this kind of continuation are identified specially in the lists of fields in the sections below. You can append any sequence of numbers onto the field and there is no set limit on how long it can be, although in extreme cases like notes_plat782348320742972403 you just might encounter the dreaded (and highly unusual) out of memory error, so don't do that. Ex-BASIC programmers might naturally use line number sequences like 1000, 1010, 1020 or 1030 etc. because they leave room to insert lines in between.

In fact these suffixes will be replaced with consecutive three-digit numbers, with leading zeros as necessary, in the rsf file generated by the run. Editing these files may be necessary to finalize system details prior to submitting the report to SPEC/HPG for review.

Fields that do not allow continuation, usually expect a certain fixed format for their value, like a date, a number, fixed range of values such as one of {base,peak,all}, or a short string such as a system or vendor name.

V.C. Free-form notes

In addition to the pre-defined fields, you can write as many notes as you wish. The benchmark, node and file server sections include notes with special suffixes, which are printed in the corresponding section of the report, using a fixed-width font:

1. notes_comp -- Notes about compiler invocation.
2. notes_port -- Notes about portability options.
3. notes_base -- Notes about base optimization options.
4. notes_peak -- Notes about peak optimization options.
5. notes -- General notes.

These may in turn be followed by an additional alphanumeric suffix, which is a generalization of the numeric suffixes described in the previous section:

   $ cat tmp.cfg
   size                 = mtest
   iterations           = 1
   output_format        = text
   teeout               = 1
   runlist              = tachyon
   tune                 = base

   notes_part_greeting_011  = ++ how
   notes_part_greeting_20   = ++ you?
   notes_part_greeting_012  = ++ are
   notes_part_aname_1       = ++ Alex,
   notes_part080            = ++ hi

   $ runspec --config tmp > /nev/dull
   $ cd ../result
   $ ls -t *mtest.txt | head -1
   MPIM2007.101.mtest.txt
   $ grep ++ *101*txt
        ++ hi
        ++ Alex,
        ++ how
        ++ are
        ++ you?
   $ 

You can optionally include an underscore just before the numeric part of the suffix, but beware: if you say both notes_plat_105 and notes_plat105, both are considered to be the same line. The last one mentioned will replace the first, and it will be the only one output.

You generally use notes to describe software or hardware details that go beyond what is captured by the predefined fields. For an example of where this might be useful, see example-medium.cfg and search for "patch". Note: some combinations of servers/browsers will refuse to open files of type .cfg; if the link does not work for you, you might be able to right-click and save the file. If the file is not found, you might try using a terminal window (aka command window, terminal emulator) to look in your installed SPEC tree, or on your SPEC distribution media in the config directory.

If no notes are filled in for a particular section, no notes are output, so you don't need to worry about making sure you have something in each section.

V.D Links in notes sections

notes_plat_001 = Additional detail may be found at
notes_plat_002 = http://www.turboblaster.com/servers/big/green/

LINK url AS [descriptive text]

notes_plat_001 = Additional detail may be found at 
notes_plat_002 = LINK http://www.turboblaster.com/servers/big/green/ AS [TurboBlaster Servers]

 Additional detail may be found at 
 TurboBlaster Servers

And in a text report, it appears as:

                                Platform Notes
                                --------------
     Additional detail may found at 
     TurboBlaster Servers (http://www.turboblaster.com/servers/big/green/)

Since the text report is not a context in which the reader can click on a link, it is spelled out instead. Note that because the text report spells the link out, the text line is wider than in HTML, PS, and PDF reports. When deciding where to break your notes lines, you'll have to pick whether to plan line widths for text (which may result in thin-looking lines elsewhere) or plan your line widths for HTML/PS/PDF (which may result in lines that fall of the right edge with text). The feature notes_wrap_columns won't help you here, since it is applied before the link is spelled out.

LINK AS is new with CPU2006 and MPI2007 V1.1

V.E Attachments

ATTACH url AS [descriptive text]

notes_plat_110 = Stated performance depends on proper cooling, as shown in the 
notes_plat_120 = ATTACH file:///Users/john/Desktop/power.jpg AS [power supply photo] 
notes_plat_130 = and ATTACH file:///Users/john/Desktop/fan.jpg AS [fan diagram] 

 Stated performance depends on proper cooling, as shown in the
 power supply photo 
 and fan diagram

And in a text report, they appear as:

                                Platform Notes
                                --------------
     Stated performance depends on proper cooling, as shown in the
     power supply photo (MPI2007.011.mtest.jpg) 
     and fan diagram (MPI2007.011.mtest.1.jpg)

In the text report, you can see that when fan.jpg and power.jpg were copied into the result directory, they were given names to show which result they correspond to: MPI2007.011.mtest.jpg and MPI2007.011.mtest.1.jpg. Note that since the text report spells the name of the attachment out, the text line is wider than in HTML, PS, and PDF reports. When deciding where to break your notes lines, you'll have to decide whether to plan line widths for text (which may result in thin-looking lines elsewhere) or plan your line widths for HTML/PS/PDF (which may result in lines that fall off the right edge with text). The feature notes_wrap_columns won't help you here, since it is applied before the attachment name is spelled out.

ATTACH is new with CPU2006 and MPI2007 V1.1

V.F Test description

Test information describes who performed the test and when. The other sections describe how the test was performed and on what system.

      test_sponsor = Genius Compilers
      tester       = Pawtuckaway State College
      system_vendor    = TurboBlaster

V.G. Benchmark description

This section of the report describes the compiling and running of the benchmarks. The first set of parameters are assigned values that have fixed formats:

The second set of parameters can be continued to multiple lines by repeating the variable name multiple times with different suffixes:

V.H. Component attributes

A system running MPI may be a standalone SMP or a cluster of nodes with dedicated file servers. The MPI2007 reporting conventions allow you to describe highly heterogeneous systems by specifying the attributes of multiple kinds of nodes, interconnects and file servers.

The output report will contain a separate section describing each of these components. Each one of these sections consists of a formatted table derived from the fixed-field entries in the config-file, followed by free-form notes derived from the notes entries of the config-file.

Each component is described with a prefix that defines its type, followed by the field to be assigned:

	node_IBM655_label = IBM 655 Server                      # This system has only one kind of node
	node_IBM655_count = 16                                  # and uses 16 of them.
	node_IBM655_count = compute,fileserver					# One of the nodes is also the file server.
	node_IBM655_notes = Node 0 is the file server for the cluster.

	node_HP2000_label = HP 2000 Server
	node_HP3000_label = HP 3000 Server                      # This system has two kinds of nodes
	node_HP2000_count = 12                                  # with different numbers of each.
	node_HP3000_count = 20
	node_HP2000_purpose = compute
	node_HP3000_purpose = compute

	interconnect_GBEthernet_data_rate = 1Gb/sec                      # Details of the GB Ethernet interconnect.
	interconnect_InfiniBand_data_rate = 1Gb/sec                      # Details of the InfiniBand interconnect.

	node_SUN1000_label = SUN 1000 Disk Array Server   # Details of the SUN 1000 file server.
	node_SUN1000_count = 1                            # Only one of them.
	node_SUN1000_purpose = fileserver

If you don't declare any components of a given type, no subsection will appear in the report. For example, on an SMT system there will be only one kind of node, and no file server, since the node uses its own local file system. The interconnect is neither replaceable nor configurable so there are no deatils to report, either.

V.I. Node description(s)

An SMP system consists of one node of one type. A heterogeneous cluster may consist of many nodes of several types. Most nodes are used for computation but others may act as file servers or provide other utilities. The fields in this section describe the hardware and software configuration of a given node, and are assigned as follows:

	node_HP2000_vendor = Hewlett-Packard Corporation

The available fixed-format fields are as follows:

Second, continuable fields:

V.J. Adaptor description(s)

The nodes in a compute-cluster use adaptors to attach to the available interconnects. The disclosure convention provides the following fields to declare multiple adaptors of different kinds for each given node type, using a second level of tags

            node_HPCX_hw_adaptor_InfiniBand_model = PCI-Express DDR InfiniBand HCA
            node_HPCX_hw_adaptor_InfiniBand_count = 1

that allow for there being different kinds of adaptors. The defined fields are

V.K. Interconnect description(s)

The nodes of a compute-cluster are joined via one or more interconnects that will transmit various kinds of data communication. The report will contain one section for each interconnect. An SMT system with no external file server will not use an interconnect for communication and file transfers, so none of the below fields will be filles in and the report will not contain any interconnect sections. The attributes of each interconnect are prefixed as follows:

	interconnect_GBEthernet_label = Gigabit Ethernet             # If more than one interconnect.
	interconnect_mpiComm_label    = MPI traffic interconnect     # It may be named by what it's used for.

First, the fixed-format fields:

Second, field names continuable as described in section V.B.

VI. Deprecated options

This section lists the configuration-file options which may be allowable in other benchmark suites that are not allowed in MPI2007.

VI.A SPEC/CPU rate runs

The MPI2007 benchmark suites deviate from the SPEC/CPU suites in that only speed runs are defined, where the time of each benchmark is measured as a single execution, as opposed to a rate run which executes multiple copies of the benchmark simultaneously. The following configuration-file options produce undefined behavior in MPI2007 and are not permitted in a submittable run:

VI.B Feedback directed optimization

The MPI2007 benchmark suites deviate from the CPU, OMP, and HPC suites in that feedback-directed compiler optimizations are not allowed. The following configuration-file options are illegal in MPI2007:

VI.C Old-style descriptive formats

A number of descriptive fields were included in earlier benchmark suites that no longer serve any purpose in generating the output reports:

VI.D Obsolete hardware designs

At least one field is a holdover from early versions of the SPEC/cpu suite, and no longer pertains to modern microprocessors:

If an mpi2007 result submission uses one of these older-style system designs, the SPEC committee may ask that the details be described in the notes section of the node.

VI.E Automatic thread-level parallelization

Some compilers provide an auto parallelization that converts loops into separate threads that execute in parallel. This is not allowed with SPEC/MPI2007, so the field

introduced in SPEC/cpu2006 and the first release of SPEC/mpi2007, is no longer used.

VII. The config file preprocessor

New with MPI2007, the tools implement a configuration file macro preprocessor. The preprocessor can be used in a variety of ways; for example to communicate settings from your shell environment into runspec:

$ cat > jan.cfg
notes01 = Today, I am happily running in directory %{MYDIR} on system %{HOST}
$ runspec --config jan --define MYDIR=$PWD --define HOST=`hostname` \
  --fakereportable fp --output_format text | grep txt
        format: ASCII -> /jan/mpi2007/result/MPI2007.090.txt
$ grep Today /jan/mpi2007/result/MPI2007.090.txt
     Today, I am happily running in directory /jan/mpi2007/config on system civilized-03
$ 

The config file preprocessor is called a macro processor because it allows you to define macros, which are brief abbreviations for longer constructs. If you've ever used the C preprocessor, the concepts will be familiar, though the syntax is slightly different.

The preprocessor is automatically run whenever you use runspec. Or, you can run it separately, as configpp, which is documented in utility.html.

Preprocessor directives begin with the percent (%) character. This character must be the first character on the line. Any amount of spaces or tabs may separate the percent from the directive.

The following are okay:

%define foo
%    define bar
%		undef hello!

The following are not okay:

# Space in the first column
 %define foo

# Tab in the first column
	%define foo

# This isn't CPP!
#define foo

VII.A Defining macros

The preprocessor is all about macros. There are no macros defined by default, so unless you define some macros, the preprocessor can't do much for you.

Macros can be defined in two ways:

1. On the command line, using the --define switch, or
2. In the configuration file, using the '%define' preprocessor directive:

   # Define a simple macro
   %define foo bar
   # Now the macro called 'foo' has the value 'bar'
   
   # It's not necessary for a macro to have a value to be useful
   %define baz
   # Now the macro called 'baz' is defined, but it has no value.
   

   Note that no quoting is necessary when specifying the names of macros or their values.

Macros defined in both ways are entirely equivalent. Because ones set on the command-line are defined first, it's not possible to use the command line to override a macro definition that occurs in the config file itself. It may help to think of a series of '%define' directives, one per --define, as being prepended to the config file.

The values assigned to macros do NOT follow the same quoting rules as variables in the config file. In particular, you may NOT use line continuation, line appending, or block quotes. You may have a value of arbitrary length, but in the interests of config file readability and maintainability, please keep them relatively short.

You will receive a warning if a previously defined macro is re-defined.

Macro names may only be composed of alphanumeric characters, underscores, and hyphens, and they ARE case-sensitive.

A macro that has not been defined will not be substituted. A macro that has been defined, but which has not been assigned a value, has the value "1".

VII.B Un-doing macro definition

Sometimes you want to make the preprocessor forget about a macro that you taught it. This is easily accomplished.

Macros can be undefined in two ways:

1. On the command line, using the --undef switch, or
2. In the configuration file, using the '%undef' preprocessor directive.

   %define foo bar
   # Now the macro called 'foo' has the value 'bar'
   
   %undef foo
   # Now it doesn't
   

   Note that no quoting is necessary when specifying the names of macros.

Like macro definition, the undefinition requests can't affect macros set in the config file because those definitions effectively happen after the un-definition. For this reason, command-line undefinition is basically useless; it can only undo macros also set on the command line.
So why was such a useless ability added to the tools? The writer likes orthogonality.

VII.C Using macros

By now you're probably over that initial euphoric rush that comes from wantonly defining and undefining macros, and you're looking for something more. This is it!

When you want to use the value of a macro, you refer to it by name. Unfortunately, the syntax for this is not as simple as you might hope. It's not too complicated, though; to have the preprocessor expand the macro 'foo', just write

  %{foo}

in the place where you'd like it to appear. Given the following config file snippet:

%define foo Hello!
%define bar baz
%define foobar Huh?
%define foobaz What?
%define Hello!baz Please don't do this

Here's a handy table to see the various ways you can reference these values:

Easy, right? The following is also possible:

Because macro values can only be one line long, it's not possible to use the preprocessor to macro-ize large chunks of your config file at once, as may be common practice for advanced users of CPP.

A macro that has not been defined will not be substituted. Thus the following case is the expected behavior:

$ cat tmp.cfg
OPTIMIZE = %{FOO}
$ runspec -c tmp -i mtest -T base tachyon
...
cc -c -o spec.o -DSPEC_MPI -DNDEBUG   %{FOO}   spec.c

Your C compiler probably won't know what to do with with %{FOO}. If you want to substitute an empty string, then assign it one:

$ runspec -c tmp -i mtest -T base --define FOO="" tachyon

Note that the following are NOT equivalent:

   --define FOO=""
   --define FOO

The former sets FOO to an empty string. The latter, effectively, sets it to "1".

VII.D Conditionals

Defining, undefining, and expanding macros is quite an enjoyable activity in and of itself, and can even be useful on occasion. However, conditionals add an entirely new dimension to config file processing: the ability to include and exclude entire sections of text based on macros and their values.

VII.D.1. %ifdef .. %endif

The %ifdef conditional provides a way to determine whether or not a particular macro has been defined. If the named macro has been defined, the conditional is true, and the text to the matching %endif is included in the text of the config file as evaluated by runspec. Note that the matching %endif may not necessarily be the next %endif; conditionals may be nested.

For example, given the following section of a config file:

%define foo
%ifdef %{foo}
This text will be included
%endif

%ifdef %{bar}
This text will not be included
%endif

The preprocessor would produce the following output:

This text will be included

Note especially the quoting used for the macro names in the conditional; the only time macro name quoting may be omitted is when defining or undefining it.

VII.D.2. %ifndef .. %endif

The %ifndef conditional is the converse of %ifdef; If the named macro has not been defined, the conditional is true, and the text to the matching %endif is included in the text of the config file as evaluated by runspec. Note that the matching %endif may not necessarily be the next %endif; conditionals may be nested.

Given a slightly modified version of the example from earlier:

%define foo
%ifndef %{foo}
Now THIS text will not be included
%endif

%ifndef %{bar}
This text WILL be included
%endif

The preprocessor would produce the following output:

This text WILL be included

VII.D.3. %if .. %endif

Checking whether or not a macro is defined is quite useful, but it's just a subset of the more general conditional facility available. This general form is

%if expression
...
%endif

The expression is evaluated using a subset of the Perl interpreter, so the possibilities for testing values are fairly broad. For example,

%ifdef %{foo}
...
%endif

is exactly equivalent to

%if defined(%{foo})
...
%endif

Likewise,

%ifndef %{foo}
...
%endif

is exactly equivalent to

%if !defined(%{foo})
...
%endif

Using the general form, it's possible to string conditionals together:

%if defined(%{foo}) && !defined(%{bar}) || %{baz} == 0
...
%endif

If a macro contains a string value, you must supply quotes:

%if '%{foo}' eq 'Hello, Dave.'
...
%endif

You may also perform basic math on macro values:

%if %{foo} * 2004 > 3737
...
%endif

More precisely, the Perl operations allowed are the :base_core and :base_math bundles, with the ability to dereference and modify variables disallowed. For more details, see the source code for config.pl (the eval_pp_conditional subroutine) and Perl's own Opcode documentation.

VII.D.4. %else

It's possible to get by without the "else" part of the classic "if .. then .. else" trio, but it's not any fun. It works as you'd expect:

%define foo
%ifndef %{foo}
This text will not be included
%else
This text WILL be included (from the else clause)
%endif

The preprocessor would produce the following output:

This text WILL be included (from the else clause)

Only one %else per conditional is allowed.

VII.D.5. %elif

%elif is another convenience that's been added. For those not familiar with CPP, it's an "else if" construct. You may have as many of these as you'd like. Given:

%define foo Hello!

%if !defined(%{foo})
This text will not be included
%elif defined(%{bar})
This text won't be included either
%elif '%{foo}' eq 'Hello!'
This text WILL be included (from the second elif clause)
%else
Alas, the else here is left out as well.
%endif

The preprocessor would produce the following output:

This text WILL be included (from the second elif clause)

VII.E Informational Directives

It's often helpful to be able to warn or abort on certain conditions. Perhaps there's a macro that must be set to a particular value, or maybe it's just very highly recommended.

VII.E.1. %warning

%warning does just what you'd expect; when the preprocessor encounters this directive, it prints the text following to stderr, along with its location within the file being read, and continues on.

Consider:

%if !defined(%{somewhat_important_macro})
% warning
% warning You have not defined somewhat_important_macro!
% warning
%endif

When run through the preprocessor, this yields the following output:

  $ configpp -c warning.cfg
  runspec v2.20 - Copyright 1999-2003 Standard Performance Evaluation Corporation
  Loading standard modules.................
  Loading runspec modules..............
  Locating benchmarks...found 13 benchmarks in 1 benchset.
  Locating output formats: text...config...html...mail...pdf...ps...raw...screen...
  WARNING: 
  WARNING: You have not defined somewhat_important_macro!
  WARNING: 
  Pre-processed configuration file dump follows:
  --------------------------------------------------------------------
  # Invocation command line:
  # /Users/cloyce/SPEC/mpi2007/bin/configpp --configpp -c warning.cfg
  ############################################################################

  --------------------------------------------------------------------

  The log for this run is in result/MPI2007.013.log

  runspec finished at Tue Apr  1 08:55:36 2003; 5 total seconds elapsed

The blank warning lines were added to make the warning stand out a little; as you can see, it's easy for it to be lost in the rest of the output.

VII.E.2. %error

Like %warning, %error logs an error to stderr and the log file. Unlike %warning, though, it then aborts the run.

Consider a slightly modified version of the previous example:

%if !defined(%{REALLY_important_macro})
% error You have not defined REALLY_important_macro!
%endif

When run through the preprocessor, this yields the following output:

  $ configpp -c error.cfg
  runspec v2.20 - Copyright 1999-2003 Standard Performance Evaluation Corporation
  Loading standard modules.................
  Loading runspec modules..............
  Locating benchmarks...found 13 benchmarks in 1 benchset.
  Locating output formats: text...config...html...mail...pdf...ps...raw...screen...
  ERROR: You have not defined somewhat_important_macro!

  The log for this run is in result/MPI2007.014.log

  runspec finished at Tue Apr  1 09:00:06 2003; 4 total seconds elapsed

  $ echo $?
  1

The ERROR line also tends to get a little lost in the visual clutter, but unlike a warning, it will be close to the last thing output. As you can see from the output of 'echo $?', runspec has exited with an error code 1.

VIII. Output files - and how they relate to your config file

This section describes how the location and contents of several kinds of output files are influenced by your config file.

VIII.A. Automatic backup of config files

It was mentioned above that the MD5 section of the config file is written automatically by the tools. Each time your config file is updated, a backup copy is made. Thus your config directory may soon come to look like this:

   $ cd $SPEC/config
   $ ls tmp.cfg*
   tmp.cfg                   tmp.cfg.2007-05-11_0842   tmp.cfg.2007-05-11_1631
   tmp.cfg.2007-05-10_2007   tmp.cfg.2007-05-11_0847   tmp.cfg.2007-05-11_1632
   tmp.cfg.2007-05-10_2010   tmp.cfg.2007-05-11_0853   tmp.cfg.2007-05-11_1731
   tmp.cfg.2007-05-10_2048   tmp.cfg.2007-05-11_0854   tmp.cfg.2007-05-11_1731a
   tmp.cfg.2007-05-10_2051   tmp.cfg.2007-05-11_0855   tmp.cfg.2007-05-12_0921
   tmp.cfg.2007-05-10_2054   tmp.cfg.2007-05-11_0856   tmp.cfg.2007-05-13_0846
   tmp.cfg.2007-05-10_2058   tmp.cfg.2007-05-11_0857   tmp.cfg.2007-05-13_0846a
   tmp.cfg.2007-05-10_2105   tmp.cfg.2007-05-11_0858   tmp.cfg.2007-05-13_0849
   tmp.cfg.2007-05-10_2105a  tmp.cfg.2007-05-11_0903   tmp.cfg.2007-05-13_0850
   tmp.cfg.2007-05-10_2106   tmp.cfg.2007-05-11_0904   tmp.cfg.2007-05-16_0957
   tmp.cfg.2007-05-10_2125   tmp.cfg.2007-05-11_0905   tmp.cfg.2007-05-18_1133
   tmp.cfg.2007-05-10_2125a  tmp.cfg.2007-05-11_0906   tmp.cfg.2007-05-19_1626
   tmp.cfg.2007-05-10_2126   tmp.cfg.2007-05-11_1348   tmp.cfg.2007-05-19_1627
   tmp.cfg.2007-05-10_2127   tmp.cfg.2007-05-11_1349   tmp.cfg.2007-05-19_1634
   tmp.cfg.2007-05-11_0811   tmp.cfg.2007-05-11_1349a  tmp.cfg.2007-05-19_1638
   tmp.cfg.2007-05-11_0823   tmp.cfg.2007-05-11_1349b  tmp.cfg.2007-05-19_1718
   tmp.cfg.2007-05-11_0835   tmp.cfg.2007-05-11_1553   tmp.cfg.2007-05-19_1720
   tmp.cfg.2007-05-11_0836   tmp.cfg.2007-05-11_1556   tmp.cfg.2007-05-19_1731
   tmp.cfg.2007-05-11_0838   tmp.cfg.2007-05-11_1557   tmp.cfg.2007-05-21_0611
   tmp.cfg.2007-05-11_0839   tmp.cfg.2007-05-11_1627   tmp.cfg.2007-05-21_0622
   tmp.cfg.2007-05-11_0840   tmp.cfg.2007-05-11_1629   tmp.cfg.2007-05-21_0652
   $

If this feels like too much clutter, you can disable the backup mechanism, as described under backup_config. Note that doing so may leave you with a risk of losing the config file in case of a filesystem overflow or system crash. A better idea may be to periodically remove just portions of the clutter, for example by typing:

   $ rm tmp.cfg.2007-05-1*
   $ ls tmp.cfg*
   tmp.cfg                  tmp.cfg.2007-05-21_0622
   tmp.cfg.2007-05-21_0611  tmp.cfg.2007-05-21_0652
   $ 

VIII.B. The log file and verbosity levels

$SPEC/result (Unix) or %SPEC%\result (Windows) contains reports and log files. When you are doing a build, you will probably find that you want to pay close attention to the log file. Depending on the verbosity level that you have selected, it will contain enormous amounts of information about how your build went.

The MPI2007 tool suite provides for varying amounts of output about its actions during a run. These levels range from the bare minimum of output (level 0) to copious streams of information almost certainly worthless to anyone not developing the tools themselves (level 99). Note: selecting one output level gives you the output from all lower levels, which may cause you to wade through more output than you might like.

VIII.B.1. Useful Search Strings

VIII.B.2. About Temporary Debug Logs

There are also temporary debug logs, such as MPI2007.001.log.debug. A debug log contains very detailed debugging output from the SPEC tools, as if --verbose 99 had been specified.

For a successful run, the debug log will be removed automatically, unless you specify "--keeptmp" on the command line, or "keeptmp=1" in your config file.

For a failed run, the debug log is kept. The debug log may seem overwhelmingly wordy, repetitive, detailed, redundant, repetitive, and long-winded, and therefore useless. Suggestion: after a failure, try looking in the regular log first, which has a default verbosity level of 5. If your regular log doesn't have as much detail as you wish, then you can examine the additional detail in the debug log.

If you file a support request, you may be asked to send in the debug log.

Temporary debug logs are new with CPU2006 and MPI2007 V1.1.

VIII.B.3. Definitions of verbosity levels

The 'level' referred to in the table below is selected either in the config file verbose option or in the runspec command as in 'runspec --verbose n'.

Levels higher than 99 are special; they are always output to your log file. You can also see them on the screen if you set verbosity to the specified level minus 100. For example, the default log level is 5. This means that on your screen you will get messages at levels 0 through 3, and 100 through 105. In your log file, you'll find find the same messages, plus the messages at levels 106 through 199.

VIII.C. Help, I've got too many logs!

If you do a very large number of builds and runs, you may find that your result directory gets far too cluttered. If it does, you should feel free to issue commands such as these on Unix systems:

   cd $SPEC
   mv result result_old
   mkdir result

On Windows, you could say:

   cd %SPEC%
   rename result result_old
   mkdir result

VIII.D. Finding the build directory

As described under "About Disk Usage" in runspec.html, the MPI2007 tools do the actual builds and runs in the run directories. The benchmark sources are never modified in the src directory.

The build directories for a benchmark are located underneath that benchmarks' top-level directory, typically $SPEC/benchspec/MPI2007/nnn.benchmark/build (Unix) or %SPEC%\benchspec\MPI2007\nnn.benchmark\build (Windows).

(If you are using the output_root feature, then the first part of that path will change to be your requested root instead of SPEC; and if you change the default for build_in_builddir, then the last part of that path will be run instead of build.)

New with MPI2007, the build directories have logical names, typically of the form build_<tune>_<extension>.0000. For example, after the command runspec --config jun09a --action build --tune base leslie3d, the following directory was created:

$ cd $SPEC/benchspec/MPI2007/107.leslie3d/run
$ pwd
/spec/joelw/benchspec/MPI2007/107.leslie3d/run
$ ls -ld build*jun*
drwxrwxr-x   2 joelw ptg    1536 Jun 10 14:49 build_base_jun09a.0000
$ 

On Windows, you would say cd %SPEC%\benchspec\MPI2007\107.leslie3d\run followed by dir build*.

If the directory build_<tune>_<extension>.0000 already exists when a new build is attempted for the same tuning and extension, the directory will be re-used, unless:

• You have set the environment variable SPEC_MPI2007_NO_RUNDIR_DEL, or
• The directory has been left in a "locked" state by an aborted previous build.

In such cases, the 0000 will be incremented until a name is generated that is available. You can find locked directories by searching for lock=1 in the file $SPEC/benchspec/MPI2007/<nnn.benchmark>/run/list (Unix) or %SPEC%\benchspec\MPI2007\<nnn.benchmark>\run\list (Windows).

When more than one build directory has been created for a given tuning and extension, you may need to trace the directory back to the specific build attempt that created it. You can do so by searching for the directory name in the log files:

$ grep Building *log | grep build_base_jun09a.0001
MPI2007.380.log:  Building 107.leslie3d mref base jun09a default: (build_base_jun09a.0001)
$ 

In the above example, the grep command locates log #380 as the log that corresponds to this run directory. On Windows, of course, you would use findstr instead of grep.

VIII.E. Files in the build directory

A variety of files are output to the build directory. Here are some of the key files which can usefully be examined:

VIII.F. For more information

For more information about how the run directories work, see the descriptions of specinvoke, specmake, and specdiff in utility.html.

IX. About Alternate Sources

Sometimes a portability issue may require use of alternative source code for a benchmark, and SPEC may issue the alternate as a "src.alt". The effect of applying a src.alt is to modify the sources in the build directory. This chapter provides an example of applying a src.alt, and introduces development of src.alts.

IX.A. Example: Applying a src.alt

This change is necessary when building 400.perlbench using GCC (or GCC-
compatibile) compilers on newer versions of Solaris.  

The diff is quite large, but the change is easy to describe.  All of the 
code in the PerlIOStdio_invalidate_fileno() function in perlio.c which 
was protected by __sun__ is replaced by the following line:

  return 0;

This makes this section of the code consistent with the code as it stands
in the standard distribution of Perl 5.10.0, and the behavior identical to
the behavior when compiled with Sun Studio.

Having downloaded the src.alt file from www.spec.org/cpu2006/src.alt, we apply it per the instructions (found in the same README from which the above paragraphs were excerpted):

$ . ./shrc

$ specbzip2 -dc 400.perlbench.solaris_gcc.cpu2006.v1.0.tar.bz2 | spectar -xf  -

Let's set up two build directories - one without the change:

$ cat $SPEC/config/without.cfg
ext          = without
$

$ runspec --action buildsetup -T base -c without -v 1 400.perlbench

runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'solaris-sparc' tools
Reading MANIFEST... 17935 files
Loading runspec modules...............
Locating benchmarks...Reading config file '/bench/cpu2006/1.0.1/config/without.cfg'
Benchmarks selected: 400.perlbench

The log for this run is in /bench/cpu2006/1.0.1/result/CPU2006.014.log

runspec finished at Thu Mar 20 18:41:51 2008; 10 total seconds elapsed
$ 

And a build directory with the change:

$ cat $SPEC/config/with.cfg
ext          = with
400.perlbench:
srcalt      = solaris_gcc
$ 

$ runspec --action buildsetup -T base -c with -v 1 400.perlbench
runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'solaris-sparc' tools
Reading MANIFEST... 17935 files
Loading runspec modules...............
Locating benchmarks...Reading config file '/bench/cpu2006/1.0.1/config/with.cfg'
Benchmarks selected: 400.perlbench
400.perlbench (base): Applied solaris_gcc src.alt.

The log for this run is in /bench/cpu2006/1.0.1/result/CPU2006.013.log

runspec finished at Thu Mar 20 18:41:32 2008; 9 total seconds elapsed
$

If we go look at those directories, the "with" directory has the expected change from the src.alt. As mentioned in the README above, a segment of code is removed (lines marked "-"), and return 0; is substituted (the line marked "+"):

$ diff -u build_base_without.0000/perlio.c build_base_with.0000/perlio.c

--- build_base_without.0000/perlio.c    Mon Jun  6 23:30:23 2005
+++ build_base_with.0000/perlio.c       Thu Mar 20 18:12:51 2008
@@ -2847,31 +2847,7 @@
     f->_fileno = -1;
     return 1;
 #  elif defined(__sun__)
-#    if defined(_LP64)
-    /* On solaris, if _LP64 is defined, the FILE structure is this:
-     *
-     *  struct FILE {
-     *      long __pad[16];
-     *  };
-     *
-     * It turns out that the fd is stored in the top 32 bits of
-     * file->__pad[4]. The lower 32 bits contain flags. file->pad[5] appears
-     * to contain a pointer or offset into another structure. All the
-     * remaining fields are zero.
-     *
-     * We set the top bits to -1 (0xFFFFFFFF).
-     */
-    f->__pad[4] |= 0xffffffff00000000L;
-    assert(fileno(f) == 0xffffffff);
-#    else /* !defined(_LP64) */
-    /* _file is just a unsigned char :-(
-       Not clear why we dup() rather than using -1
-       even if that would be treated as 0xFF - so will
-       a dup fail ...
-     */
-    f->_file = PerlLIO_dup(fileno(f));
-#    endif /* defined(_LP64) */
-    return 1;
+    return 0;
 #  elif defined(__hpux)
     f->__fileH = 0xff;
     f->__fileL = 0xff;
@@ -5056,11 +5032,3 @@
     return result;
 }
 #endif

IX.B. Developing a src.alt (brief introduction)

If you are trying to create a new alternative source, you should become familiar with how to work in a sandbox, temporarily abandoning the tools during your development phase. (Or, you can use convert_to_development to make the whole installation into one big sandbox.) Once you have developed your alternative source, you'll want to package it up with makesrcalt, and you'll need to contact SPEC to get the source approved. The convert_to_development utility is new with CPU2006 and MPI2007 V1.1, and makesrcalt is newly documented. Both are much more fully discussed in utility.html.

X. Troubleshooting

When something goes wrong with a build, here are some things to check:

1. Are there any obvious clues in the log file? Search for the word "Building". Keep searching until you hit the next benchmark AFTER the one that you are interested in. Now scroll backward one screen's worth of text.

2. Did your desired switches get applied? Go to the build directory, and look at options*out.

3. Did the tools or your compilers report any errors? Look in the build directory at *err.

4. What happens if you try the build by hand? See the section on specmake in utility.html.

5. If an actual run fails, what happens if you invoke the run by hand? See the information about "specinvoke -n" in utility.html

6. Do you understand what is in your path, and why? Sometimes confusion can be greatly reduced by ensuring that you have only what is needed, avoiding, in particular, experimental and non-standard versions of standard utilities.

7. Try asking the tools to leave more clues behind, with keeptmp.

Copyright © 1999-2010 Standard Performance Evaluation Corporation
All Rights Reserved