Last updated: $Date: 2008-06-17 12:36:11 -0400 (Tue, 17 Jun 2008) $ by $Author: cloyce $
(To check for possible updates to this document, please
see http://www.spec.org/cpu2006/Docs/ )
Contents
The SPEC CPU2006 suite has been tested under Unix, Linux, Mac OS X and Windows XP/Vista systems. Your DVD can be installed under many operating systems.
Reminder: the SPEC license allows you to install on multiple systems as you may wish within your institution; but you may not share the software with the public.
This document covers the installation procedure for SPEC CPU2006 under Microsoft Windows.
Note: Unless otherwise specified, refererences to "Windows" in this document apply to Windows XP, Windows Vista and Windows Server. Later and/or earlier versions of Windows/NT-based systems (such as Windows 2000) might also work, but have not been tested. Windows/98 and Windows/Me will definitely not work.
The installation procedure for Windows is as follows:
Review the hardware and software requirements, in system-requirements.html
Note: links to SPEC CPU2006 documents on this web page assume that you are reading the page from a directory that also contains the other SPEC CPU2006 documents. If by some chance you are reading this web page from a location where the links do not work, try accessing the referenced documents at one of the following locations:
Note: the steps that follow assume that your DVD drive is on the same system as where you wish to install. If it is on a different system, please see the appendix.
Open a Command Prompt window (formerly known as an "MSDOS Window"). Typically, this is done by
selecting:
Start-->All Programs-->Accessories-->Command Prompt.
Adjust the properties to allow you to see plenty of lines scrolled off the top (for example, 9000). Click the upper left corner of the Command Prompt window, scroll down to "Properties", click the "Layout" tab, and in the section labelled "Screen Buffer Size" enter a new value for "Height".
Check to see whether or not the temp environment variable points to a directory that can be used to hold temporary files.
C:\> echo %temp% %temp%
If it's unset (just prints %temp%), you should set it to the full path (with drive letter) of a directory that can be used as scratch space. For example, if Kumaran would like to use a temporary directory underneath his directory on drive K:, he could type:
C:\> set temp=K:\KUMARAN\TEMP
Decide where you want to install the CPU2006 suite. You should make sure that your chosen destination disk has at least 8GB free. (For more information on disk usage, see system-requirements.html.) For the following examples, we will assume that your destination is on drive C:, in the directory \cpu2006.
Change to the DVD directory. For the following examples, we'll assume that your DVD is mounted on drive D:, so entering just the letter and a colon gets us to that drive:
C:\> D: D:\>
You're now ready to run the installer. The format for this command is
install.bat destination_drive\destination_directory
For example, if your DVD is in drive D:, and you want to install CPU2006 on drive C: in a folder named cpu2006, you could type:
D:\> install.bat C:\cpu2006
You should see a message similar to the following:
Installing FROM D:\ Installation completed! If this is NOT correct, abort the process by hitting Control-C and run install.bat from the correct benchmark tree. Press any key to continue . . .
If you see a message similar to the above, just press return.
If you receive an error message such as:
Access is denied
then please verify that %temp% is defined (see above).
Now that the source directory has been verified, the SPEC tools will ask you to confirm the destination folder.
You should see a message similar to the following:
Installing TO "C:\cpu2006" If this is NOT correct, abort the process by hitting Control-C and specify the desired installation path as a parameter to install.bat, for example: D:\install.bat C:\SPEC\cpu2006 Press any key to continue . . .
If you see a message similar to the above, just press return.
If all goes well, the SPEC tools will inform you that the benchmark is being unpacked. Please be patient - although only a few messages are printed, thousands of files are installed:
Installing from "D:\" Installing to "C:\cpu2006\" Depending on the speed of the drive holding your installation media and the speed of your destination disk, this may take more than 5 minutes. Please be patient. Unpacking CPU2006 base files (125.5 MB) Unpacking 400.perlbench benchmark and data files (61.5 MB) Unpacking 401.bzip2 benchmark and data files (110.7 MB) Unpacking 403.gcc benchmark and data files (43 MB) . . . Checking the integrity of your source tree... Depending on the amount of memory in your system, and the speed of your destination disk, this may take more than 10 minutes. Please be patient. Unpacking tools binaries Setting SPEC environment variable to c:\cpu2006\ Checking the integrity of your binary tools... Testing the tools installation (this may take a minute) Runspec tests completed successfully! Installation completed!
The installation will consume around 1.5GB on your destination disk.
After this step completes, you will find yourself in the destination directory that you selected.
Read the comments in the file
shrc.bat
and make the appropriate edits for your compiler paths.
Caution: you may find that the lines are not correctly formatted (the text appears to be all run together) when you edit this file. If so, see the section below: Using Text Files on Windows.
You will have to uncomment one of two lines:
rem set SHRC_COMPILER_PATH_SET=yes
or
rem set SHRC_PRECOMPILED=yes
by removing "rem" from the beginning of the desired line.
If you uncomment the first line, you will have to follow the instructions a few lines further on, to set up the environment for your compiler.
If you uncomment the second line, you must have pre-compiled binaries for the benchmarks
Note that it is, in general, a good idea to ensure that you understand what is in your path, and that you have only what you truly need. If you have non-standard versions of commonly used utilities in your path, you may avoid unpleasant surprises by taking them out. In order to help you understand your path, shrc.bat will print it after it is done.
Set the environment, using your edited shrc. For example:
C:\cpu2006> shrc.bat
Test that you can build a benchmark using the config file supplied for your system. Example config files can be found in %SPEC%\config. (For an introduction to config files, see "About Config Files" in runspec.html.)
In the examples below, "^" (often called "hat" or "carat") indicates line continuation:
For example, on a Windows system with the 64-bit PGI compilers installed, you could use the command:
C:\cpu2006> runspec --action=build --tune=base ^
More? --config=Example-windows64-amd64-pgi.cfg 401.bzip2
The --tune=base indicates that we want to use only the simple tuning, if the config file contains more than one kind of tuning.
Test that you can run a benchmark, using the minimal input set - the "test" workload.
C:\cpu2006> runspec --size=test --iterations=1 --noreportable ^
More? --tune=base --config=Example-windows64-amd64-pgi.cfg 401.bzip2
The --noreportable ensures that the tools will allow us to run just a single benchmark instead of the whole suite.
Test that you can run a benchmark using the real input set - the "reference" workload. For example:
C:\cpu2006> runspec --size=ref --iterations=1 --noreportable ^
More? --tune=base --config=Example-windows64-amd64-pgi.cfg 401.bzip2
To run an official run of the integer suite with simple (baseline) tuning:
C:\cpu2006> runspec --tune=base --config=Example-windows64-amd64-pgi.cfg int
To run an official run of the floating point suite with simple (baseline) tuning:
C:\cpu2006> runspec --tune=base --config=Example-windows64-amd64-pgi.cfg fp
To run an official run of both the integer and floating point suites with simple (baseline) tuning:
C:\cpu2006> runspec --tune=base --config=Example-windows64-amd64-pgi.cfg all
Have a look at runspec.html to learn more about using runspec.
There are many files in the SPEC CPU2006 kit that contain text. Unfortunately, Unix systems and Windows systems have different conventions for storing text files. Sometimes, a text file formatted for Windows will appear on Unix as if it has extra Control-M characters. Sometimes, a text file formatted for Unix will appear on Windows as if all the lines were joined together.
There are at least three ways for Windows users to correctly view and edit text files that originated on a Unix system:
Use WordPad. WordPad can commonly be found by
Start-->All Programs-->Accessories-->WordPad
Use a Command Prompt and type "Edit". This alternative works only if the file has a short name with 8 characters or fewer, a dot, and then 3 characters or fewer. If you are trying to use Edit with a longer file name, you can discover that there is an "8 dot 3" synonym for it by typing: "dir /x".
Use the editor "vi". Although vi originated on Unix systems, it is also often found on Windows systems. For example:
There is a free ("charityware") version with some non-traditional features known as "Vi IMproved" (at http://www.vim.org/).
There is a version with the traditional Unix features in the MKS Toolkit (http://www.datafocus.com/products/tk/).
Also, there was a version with a subset of the traditional Unix vi features in the "Microsoft Windows Windows Workstation 4.0 Resource Kit" (information available at http://mspress.microsoft.com); perhaps later resource kit versions also have it, but this has not been checked.
Note that mention of these versions of vi is not intended as an endorsement by SPEC.
Here is a complete Windows installation, with commentary. We assume that Steps 1 and 2 are already done (from the list of Installation Steps earlier in this document).
Step 3: Check the temp environment variable.
C:\>echo %temp% C:\TEMP
Step 4: Create a place for the suite, and check space.
C:\>C:
C:\>mkdir cpu2006
C:\>cd cpu2006
C:\cpu2006>dir
Volume in drive C has no label.
Volume Serial Number is 6874-0B55
Directory of C:\cpu2006
10/16/2007 05:13 PM <DIR> .
10/16/2007 05:13 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 5,776,879,616 bytes free
Note that we have about 6GB of space on the destination drive, which is a bit smaller than recommended. This is enough space to demonstrate an installation, but would quickly fill up for actual "reportable" runs.
Step 5: change to the drive where the DVD is mounted
C:\cpu2006>d:
Step 6: Actually do the installation.
D:\>install.bat C:\cpu2006 Installing FROM D:\ If this is NOT correct, abort the process by hitting Control-C and run install.bat from the correct benchmark tree. Press any key to continue . . . Installing TO "C:\cpu2006" If this is NOT correct, abort the process by hitting Control-C and specify the desired installation path as a parameter to install.bat, either as (for example) U:\install.bat C:\SPEC\cpu2006 Press any key to continue . . . Installing from "D:\" Installing to "C:\cpu2006\" Depending on the speed of the drive holding your installation media and the speed of your destination disk, this may take more than 5 minutes. Please be patient. Unpacking CPU2006 base files (125.5 MB) Unpacking 400.perlbench benchmark and data files (61.5 MB) Unpacking 401.bzip2 benchmark and data files (110.7 MB) Unpacking 403.gcc benchmark and data files (43 MB) Unpacking 410.bwaves benchmark and data files (0.1 MB) Unpacking 416.gamess benchmark and data files (16.8 MB) Unpacking 429.mcf benchmark and data files (6.9 MB) Unpacking 433.milc benchmark and data files (0.6 MB) Unpacking 434.zeusmp benchmark and data files (1.1 MB) Unpacking 435.gromacs benchmark and data files (13 MB) Unpacking 436.cactusADM benchmark and data files (3.3 MB) Unpacking 437.leslie3d benchmark and data files (0.3 MB) Unpacking 444.namd benchmark and data files (7.6 MB) Unpacking 445.gobmk benchmark and data files (9.2 MB) Unpacking 447.dealII benchmark and data files (70.2 MB) Unpacking 450.soplex benchmark and data files (321 MB) Unpacking 453.povray benchmark and data files (10.3 MB) Unpacking 454.calculix benchmark and data files (26 MB) Unpacking 456.hmmer benchmark and data files (57 MB) Unpacking 458.sjeng benchmark and data files (0.4 MB) Unpacking 459.GemsFDTD benchmark and data files (2.6 MB) Unpacking 462.libquantum benchmark and data files (0.2 MB) Unpacking 464.h264ref benchmark and data files (52.9 MB) Unpacking 465.tonto benchmark and data files (6.9 MB) Unpacking 470.lbm benchmark and data files (4.7 MB) Unpacking 471.omnetpp benchmark and data files (2.8 MB) Unpacking 473.astar benchmark and data files (5.8 MB) Unpacking 481.wrf benchmark and data files (67.1 MB) Unpacking 482.sphinx3 benchmark and data files (51.7 MB) Unpacking 483.xalancbmk benchmark and data files (213.7 MB) Unpacking 998.specrand benchmark and data files (4.1 MB) Unpacking 999.specrand benchmark and data files (4.1 MB) Unpacking tools source files (88 MB) Checking the integrity of your source tree... Depending on the amount of memory in your system, and the speed of your destination disk, this may take more than 10 minutes. Please be patient. Unpacking tools binaries Setting SPEC environment variable to c:\cpu2006\ Checking the integrity of your binary tools... Testing the tools installation (this may take a minute) Runspec tests completed successfully! Installation completed!
Step 7: Edit shrc.bat. This was done in a notepad session, which is not shown, but the "fc" command is used below to compare the original shrc.bat to our modified copy:
C:\cpu2006>copy shrc.bat shrc.bat.as-distributed
1 file(s) copied.
C:\cpu2006>notepad shrc.bat
C:\cpu2006>fc shrc.bat.as-distributed shrc.bat
Comparing files shrc.bat.as-distributed and SHRC.BAT
***** shrc.bat.as-distributed
rem the line that follows (just remove the word 'rem').
rem set SHRC_COMPILER_PATH_SET=yes
rem
***** SHRC.BAT
rem the line that follows (just remove the word 'rem').
set SHRC_COMPILER_PATH_SET=yes
rem
*****
***** shrc.bat.as-distributed
rem or possibly even
rem call "c:\program files\Intel\Compiler\C++\9.1\IA32\Bin\iclvars.bat"
***** SHRC.BAT
rem or possibly even
call "c:\Program Files\Intel\Compiler\C++\10.0.025\IA32\Bin\iclvars.bat"
call "c:\Program Files\Intel\Compiler\Fortran\10.0.025\IA32\Bin\ifortvars.bat"
*****
Step 8: set the environment
C:\cpu2006>shrc Intel(R) C++ Compiler for applications running IA-32, Version 10.0.025 Copyright (C) 1985-2007 Intel Corporation. All rights reserved. Setting environment for using Microsoft Visual Studio .NET 2003 tools. (If you have another version of Visual Studio or Visual C++ installed and wish to use its tools from the command line, run vcvars32.bat for that version.) Intel(R) Fortran Compiler for applications running on IA-32, Version 10.0.025 Copyright (C) 1985-2007 Intel Corporation. All rights reserved. Setting environment for using Microsoft Visual Studio .NET 2003 tools. (If you have another version of Visual Studio or Visual C++ installed and wish to use its tools from the command line, run vcvars32.bat for that version.) PATH=^ C:\cpu2006\bin\windows;^ C:\cpu2006\bin;^ C:\Program Files\Intel\Compiler\Fortran\10.0.025\Ia32\Bin;^ C:\Program Files\Common Files\Intel\Shared Files\Ia32\Bin;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;^ c:\Program Files\Microsoft Visual Studio .NET 2003\VC7\BIN;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin\prerelease;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin;^ c:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;^ c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322;^ C:\Program Files\Intel\Compiler\C++\10.0.025\\Ia32\Bin;^ C:\Program Files\Common Files\Intel\Shared Files\Ia32\Bin;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;^ c:\Program Files\Microsoft Visual Studio .NET 2003\VC7\BIN;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin\prerelease;^ c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin;^ c:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;^ c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322;^ "c:\cpu2006\\bin";^ C:\Program Files\Intel\VTune\CGGlbCache;^ C:\Program Files\Intel\VTune\Shared\Bin;^ C:\Program Files\Common Files\Intel\Shared Files\IDVC;^ C:\Program Files\Intel\VTune\Analyzer\Bin;^ C:\WINDOWS\system32;^ C:\WINDOWS;^ C:\WINDOWS\system32\WBEM;^ C:\Program Files\Intel\MKL\8.0\ia32\bin;^ C:\Program Files\Common Files\Roxio Shared\DLLShared;^ c:\program files\windows nt\accessories;^ c:\emon\bin;^ C:\Program Files\Intel\DMIX;^ C:\Program Files\QuickTime\QTSystem\;^ C:\Program Files\Intel\Compiler\Fortran\10.0.025\\IA32\Lib D:\cpu2006>icl -V Intel(R) C++ Compiler for applications running on IA-32, Version 10.0 Build 20070426 Package ID: W_CC_P_10.0.025 Copyright (C) 1985-2007 Intel Corporation. All rights reserved. icl: command line warning #10155: ignoring option '/V'; argument required icl: command line error: no files specified; for help type "icl /help"
Step 9. Use runspec to do a test build:
C:\cpu2006>runspec --action=build --tune=base --config=Example-windows-ia32-icl.cfg 401.bzip2
runspec v5552 - Copyright 1999-2007 Standard Performance Evaluation Corporation
Using 'windows-i386 ' tools
Reading MANIFEST... 18457 files
Loading runspec modules................
Locating benchmarks...found 31 benchmarks in 13 benchsets.
=============================================================================
Warning: You appear to be using one of the config files that is supplied
with the SPEC CPU2006 distribution. This can be a fine way to get started.
Each config file was developed for a specific combination of compiler / OS /
hardware. If your platform uses different versions of the software or
hardware listed, or operates in a different mode (e.g. 32- vs. 64-bit mode),
there is the possibility that this configuration file may not work as-is. If
problems arise please see the technical support file at
http://www.spec.org/cpu2006/Docs/techsupport.html
A more recent config file for your platform may be among result submissions at
http://www.spec.org/cpu2006/
Generally, issues with compilation should be directed to the compiler vendor.
You can find hints about how to debug problems by looking at the section on
"Troubleshooting" in
http://www.spec.org/cpu2006/Docs/config.html
This warning will go away if you rename your config file to something other
than one of the names of the presupplied config files.
==================== The run will continue in 30 seconds ====================
Reading config file 'C:/cpu2006/config/Example-windows-ia32-icl.cfg'
Loading "http://www.spec.org/auto/cpu2006/devel_version" for version check: FAILED
NOTICE: Suite version checking failed; got
500 Can't connect to www.spec.org:80 (connect: Unknown error)
A connection to the internet is not required in order to run
CPU2006. However, if one is available, several components will
be checked to see if they are current. If you need to use an
HTTP proxy to access the Internet, please see the 'http_proxy'
entry in config.html.
----------------------------------
The run will continue in 5 seconds
----------------------------------
Benchmarks selected: 401.bzip2
Compiling Binaries
Building 401.bzip2 ref base cpu2006.win32.fast.exe default: (build_base_cpu2006.win32.fast.exe.0000)
Build successes: 401.bzip2(base)
Build Complete
The log for this run is in C:\cpu2006/result/CPU2006.001.log
runspec finished at Tue Oct 16 19:03:59 2007; 74 total seconds elapsed
C:\cpu2006>
At this point, we've accomplished a lot. The SPEC tree is installed, and we have verified that a benchmark can be compiled using the installed C compiler.
Step 10. Now try running that benchmark, using the minimal test workload. The test workload runs in a tiny amount of time and does a minimal verification that the benchmark executable can at least start up:
C:\cpu2006>runspec --size=test --iterations=1 --noreportable ^
More? --config=Example-windows-ia32-icl.cfg 401.bzip2
runspec v5552 - Copyright 1999-2007 Standard Performance Evaluation Corporation
Using 'windows-i386 ' tools
Reading MANIFEST... 18457 files
Loading runspec modules................
Locating benchmarks...found 31 benchmarks in 13 benchsets.
=============================================================================
Warning: You appear to be using one of the config files that is supplied
with the SPEC CPU2006 distribution. This can be a fine way to get started.
Each config file was developed for a specific combination of compiler / OS /
hardware. If your platform uses different versions of the software or
hardware listed, or operates in a different mode (e.g. 32- vs. 64-bit mode),
there is the possibility that this configuration file may not work as-is. If
problems arise please see the technical support file at
http://www.spec.org/cpu2006/Docs/techsupport.html
A more recent config file for your platform may be among result submissions at
http://www.spec.org/cpu2006/
Generally, issues with compilation should be directed to the compiler vendor.
You can find hints about how to debug problems by looking at the section on
"Troubleshooting" in
http://www.spec.org/cpu2006/Docs/config.html
This warning will go away if you rename your config file to something other
than one of the names of the presupplied config files.
==================== The run will continue in 30 seconds ====================
Reading config file 'C:/cpu2006/config/Example-windows-ia32-icl.cfg'
Benchmarks selected: 401.bzip2
Compiling Binaries
Up to date 401.bzip2 test base cpu2006.win32.fast.exe default
Setting Up Run Directories
Setting up 401.bzip2 test base cpu2006.win32.fast.exe default: created (run_base_test_cpu2006.win32.fast.exe.0000)
Running Benchmarks
Running 401.bzip2 test base cpu2006.win32.fast.exe default
Success: 1x401.bzip2
Producing Raw Reports
mach: default
ext: cpu2006.win32.fast.exe
size: test
set: int
format: raw -> C:/cpu2006/result/CINT2006.002.test.rsf
Parsing flags for 401.bzip2 base: done
Doing flag reduction: done
format: flags -> C:/cpu2006/result/CINT2006.002.test.flags.html
format: ASCII -> C:/cpu2006/result/CINT2006.002.test.txt
format: HTML -> C:/cpu2006/result/CINT2006.002.test.html, result//invalid.gif, CINT2006.002.test.gif
set: fp
The log for this run is in C:\cpu2006/result/CPU2006.002.log
runspec finished at Tue Oct 16 19:08:51 2007; 54 total seconds elapsed
Notice about 19 lines up where it says "Success: 1x401.bzip2". That is what we want to see.
Step 11. So, let's try running 401.bzip2 with the real workload. This is going to take a while - on the system used for the sample installation, about 15 minutes.
C:\cpu2006>runspec --size=ref --iterations=1 --noreportable --tune=base ^
More? --config=Example-windows-ia32-icl.cfg 401.bzip2
runspec v5552 - Copyright 1999-2007 Standard Performance Evaluation Corporation
Using 'windows-i386 ' tools
Reading MANIFEST... 18457 files
Loading runspec modules................
Locating benchmarks...found 31 benchmarks in 13 benchsets.
=============================================================================
Warning: You appear to be using one of the config files that is supplied
with the SPEC CPU2006 distribution. This can be a fine way to get started.
Each config file was developed for a specific combination of compiler / OS /
hardware. If your platform uses different versions of the software or
hardware listed, or operates in a different mode (e.g. 32- vs. 64-bit mode),
there is the possibility that this configuration file may not work as-is. If
problems arise please see the technical support file at
http://www.spec.org/cpu2006/Docs/techsupport.html
A more recent config file for your platform may be among result submissions at
http://www.spec.org/cpu2006/
Generally, issues with compilation should be directed to the compiler vendor.
You can find hints about how to debug problems by looking at the section on
"Troubleshooting" in
http://www.spec.org/cpu2006/Docs/config.html
This warning will go away if you rename your config file to something other
than one of the names of the presupplied config files.
==================== The run will continue in 30 seconds ====================
Reading config file 'C:/cpu2006/config/Example-windows-ia32-icl.cfg'
Benchmarks selected: 401.bzip2
Compiling Binaries
Up to date 401.bzip2 ref base cpu2006.win32.fast.exe default
Setting Up Run Directories
Setting up 401.bzip2 ref base cpu2006.win32.fast.exe default: created (run_base_ref_cpu2006.win32.fast.exe.0000)
Running Benchmarks
Running 401.bzip2 ref base cpu2006.win32.fast.exe default
Success: 1x401.bzip2
Producing Raw Reports
mach: default
ext: cpu2006.win32.fast.exe
size: ref
set: int
format: raw -> C:/cpu2006/result/CINT2006.003.ref.rsf
Parsing flags for 401.bzip2 base: done
Doing flag reduction: done
format: flags -> C:/cpu2006/result/CINT2006.003.ref.flags.html
format: ASCII -> C:/cpu2006/result/CINT2006.003.ref.txt
format: HTML -> C:/cpu2006/result/CINT2006.003.ref.html, CINT2006.003.ref.gif
set: fp
The log for this run is in C:\cpu2006/result/CPU2006.003.log
runspec finished at Tue Oct 16 19:26:06 2007; 971 total seconds elapsed
Success with the real workload! So now let's look in the result directory and see what we find:
C:\cpu2006>cd result
C:\cpu2006\result>dir
Volume in drive C has no label.
Volume Serial Number is 6874-0B55
Directory of C:\cpu2006\result
10/16/2007 07:26 PM <DIR> .
10/16/2007 07:26 PM <DIR> ..
10/16/2007 07:08 PM 21,590 CINT2006.002.test.flags.html
10/16/2007 07:08 PM 3,815 CINT2006.002.test.gif
10/16/2007 07:08 PM 44,738 CINT2006.002.test.html
10/16/2007 07:08 PM 9,078 CINT2006.002.test.rsf
10/16/2007 07:08 PM 8,539 CINT2006.002.test.txt
10/16/2007 07:26 PM 21,590 CINT2006.003.ref.flags.html
10/16/2007 07:26 PM 4,548 CINT2006.003.ref.gif
10/16/2007 07:26 PM 44,727 CINT2006.003.ref.html
10/16/2007 07:26 PM 8,990 CINT2006.003.ref.rsf
10/16/2007 07:26 PM 8,379 CINT2006.003.ref.txt
10/16/2007 07:03 PM 15,406 CPU2006.001.log
10/16/2007 07:08 PM 5,208 CPU2006.002.log
10/16/2007 07:26 PM 6,611 CPU2006.003.log
10/16/2007 07:10 PM 5 lock.CPU2006
10/16/2007 07:08 PM 8,846 invalid.gif
15 File(s) 212,070 bytes
2 Dir(s) 8,648,175,616 bytes free
Notice the log files from our runspec commands. Those runspec commands are easily extracted with "findstr":
C:\cpu2006\result>findstr /C:"runspec --" *.log CPU2006.001.log:runspec: runspec --action=build --tune=base --config=Example-windows-ia32-icl.cfg 401.bzip2 CPU2006.001.log:runspec = C:\\cpu2006\\bin\\runspec --action=build --tune=base --config=Example-windows-ia32-icl.cfg 401.bzip2 CPU2006.002.log:runspec: runspec --size=test --iterations=1 --noreportable --tune=base --config=Example-windows-ia32-icl.cfg 401.bzip2 CPU2006.003.log:runspec: runspec --size=ref --iterations=1 --noreportable --tune=base --config=Example-windows-ia32-icl.cfg 401.bzip2
Let's look at our results, in the ".txt" file:
C:\cpu2006\result>type CINT2006.003.ref.txt
##############################################################################
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
# #
# 'reportable' flag not set during run #
# 471.omnetpp base did not have enough runs! #
# 456.hmmer base did not have enough runs! #
# 445.gobmk base did not have enough runs! #
# 458.sjeng base did not have enough runs! #
# 429.mcf base did not have enough runs! #
# 473.astar base did not have enough runs! #
# 483.xalancbmk base did not have enough runs! #
# 400.perlbench base did not have enough runs! #
# 464.h264ref base did not have enough runs! #
# 462.libquantum base did not have enough runs! #
# 401.bzip2 base did not have enough runs! #
# 403.gcc base did not have enough runs! #
# Unknown flags were used! See #
# http://www.spec.org/auto/cpu2006/Docs/runspec.html#flagsurl #
# for information about how to get rid of this error. #
# #
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
##############################################################################
SPEC(R) CINT2006 Summary
Intel Corporation System Model Name
Tue Oct 16 19:09:55 2007
CPU2006 License: 0 Test date: Oct-2007
Test sponsor: Not Intel Corporation Hardware availability: Dec-9999
Tested by: Not Intel Corporation Software availability: Dec-9999
Estimated Estimated
Base Base Base Peak Peak Peak
Benchmarks Ref. Run Time Ratio Ref. Run Time Ratio
-------------- ------ --------- --------- ------ --------- ---------
400.perlbench NR
401.bzip2 9650 916 10.5 *
403.gcc NR
429.mcf NR
445.gobmk NR
456.hmmer NR
458.sjeng NR
462.libquantum NR
464.h264ref NR
471.omnetpp NR
473.astar NR
483.xalancbmk NR
==============================================================================
400.perlbench NR
401.bzip2 9650 916 10.5 *
403.gcc NR
429.mcf NR
445.gobmk NR
456.hmmer NR
458.sjeng NR
462.libquantum NR
464.h264ref NR
471.omnetpp NR
473.astar NR
483.xalancbmk NR
Est. SPECint(R)_base2006 --
Est. SPECint2006 Not Run
In the table above, most of the results are blank, because we only ran 1 of the 12 integer benchmarks.
Notice that the values for SPECint_base2006 and SPECint2006 are "--" and "Not Run"; these would be filled in if we did a "reportable" run; for information, please see "--reportable" in runspec.html
There are also lots of dashes for the various portions of the system description, both at the top of the page and in the section that follows. These dashes indicate that we have not filled in the fields that describe the hardware and software that we are testing. For information about these fields, please see config.html
HARDWARE
--------
CPU Name: Trademarked CPU Name
CPU Characteristics:
CPU MHz: 9999
FPU: Integrated
CPU(s) enabled: 9999 cores, 9999 chips, 9999 cores/chip, 9999 threads/core
CPU(s) orderable: 9999 chip
Primary Cache: 9999 K micro-ops I + 9999 KB D on chip per core
Secondary Cache: 9999 MB I+D on chip per core
L3 Cache: None
Other Cache: None
Memory: 9999 GB
Disk Subsystem: 9999 GB SATA, 9999RPM
Other Hardware: None
SOFTWARE
--------
Operating System: Windows XP x64 Professional
Compiler: Intel C++ Compiler for IA32 version 9.x
Package ID XXXXXXXX Build no XXXXXXXXX
Auto Parallel: No
File System: NTFS
System State: Default
Base Pointers: 32-bit
Peak Pointers: 32-bit
Other Software: None
Base Unknown Flags
------------------
401.bzip2: "icl -Qvc7.1 -Qc99" (in CC) "icl -Qvc7.1 -Qc99" (in LD)
"-link /FORCE:MULTIPLE" (in LDOUT) "-fast" (in OPTIMIZE)
"/F512000000" (in EXTRA_LDFLAGS) "shlw32m.lib" (in EXTRA_LIBS)
SPEC and SPECint 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.
##############################################################################
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
# #
# 'reportable' flag not set during run #
# 471.omnetpp base did not have enough runs! #
# 456.hmmer base did not have enough runs! #
# 445.gobmk base did not have enough runs! #
# 458.sjeng base did not have enough runs! #
# 429.mcf base did not have enough runs! #
# 473.astar base did not have enough runs! #
# 483.xalancbmk base did not have enough runs! #
# 400.perlbench base did not have enough runs! #
# 464.h264ref base did not have enough runs! #
# 462.libquantum base did not have enough runs! #
# 401.bzip2 base did not have enough runs! #
# 403.gcc base did not have enough runs! #
# Unknown flags were used! See #
# http://www.spec.org/auto/cpu2006/Docs/runspec.html#flagsurl #
# for information about how to get rid of this error. #
# #
# INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN #
##############################################################################
-----------------------------------------------------------------------------
For questions about this result, please contact the tester.
For other inquiries, please contact webmaster@spec.org.
Copyright 2007 Standard Performance Evaluation Corporation
Tested with SPEC CPU2006 v103.
Report generated on Tue Oct 16 19:26:05 2007 by CPU2006 ASCII formatter v5493.
Done. The suite is installed, and we can run at least one benchmark for real.
If the title of this section describes your situation, you basically have two choices.
You might be able to mount the DVD on one system and use network services to make it available on other systems.
Please note that the SPEC CPU2006 license agreement does not allow you to post the DVD on any public server. If your institution has a SPEC CPU2006 license, then it's fine to post it on an internal server that is accessible only to members of your institution.
Whether you attempt a network mount will probably depend on:
If your network environment allows easy cross-system mounting, you can use a network mount for the installation. Otherwise, you can fall back on the tar file.
Note: if you insert the DVD on a system running Unix or Linux, you may need to share it using nfs commands. This Windows installation guide does not attempt to give hints about how to do Unix nfs commands, although you will find some hints in the corresponding appendix of install-guide-unix.html. Instead, let's assume that you are using two Windows systems. System A is a Windows system with a DVD drive; System B is a Windows system where you would like to do the installation.
To do the installation:
At System A, insert the DVD.
Then, bring up a Windows Explorer window (for example, by double clicking on the My Documents icon). Click the plus sign next to My Computer and you should see the DVD drive. Let's suppose that it is drive F:.
Right-click on the DVD drive and select "Sharing and Security..."
In the box that comes up, under the "Sharing" tab, you may see a warning To protect your computer from unauthorized access, sharing the root of a dive is not recommended. If you understand the risk but still want to share the root of the drive, click here. This most informative warning is displayed for your consideration and you can proceed to consider it. If you decide that it is safe to share your DVD drive, then click where indicated.
Select "Share this folder"
Now, move to System B.
Bring up a Windows Explorer window (for example, by double clicking on the My Documents icon). Select Tools -> Map Network Drive. The Drive letter may offer a default, such as Z:. In the box for Folder, type two backslashes, the name of system A, a backslash, and its shared drive letter - for example \\SystemA\F
Continue with Step 2 above. When you get to Steps 5 and 6, remember to use the drive letter as it is known on System B - from the dialog box of a moment ago - for example
D:\Documents and Settings\Saturos\> Z: Z:\> install.bat C:\cpu2006
If the DVD drive is on a system other than the one where you wish to do the installation, and if you do not wish to try to get a network mount working, then the final fallback is to use the compressed tarfile. If you choose this option, please carefully observe the warnings.
Go to the system with the DVD drive ("System A"). Insert the SPEC CPU2006 DVD.
From a command window (aka terminal window), cd to the top level directory on the DVD.
You are going to retrieve five things from the DVD. First, find the large tarfile and its corresponding md5 file:
cd install_archives dir cpu2006.tar.bz*
or, if System A is a Unix system, then:
cd install_archives ls -l cpu2006.tar.bz*
In either case, you should see one moderately large file > 500MB, cpu2006.tar.bz2, and a small file associated with it that contains a checksum, cpu2006.tar.bz2.md5.
If you don't see the above files, try looking for cpu*tar*. The name might change if, for example, a maintenance update of CPU2006 changes the name slightly to indicate an updated version.
Do whatever is required in order to transfer both files intact to the system where you wish to do the installation ("System B"). If you use ftp, do not forget to use image (binary) mode. For example:
ftp> bin <-------- important
200 Type set to I.
ftp> put cpu2006.tar.bz2
ftp> put cpu2006.tar.bz2.md5
Please note that the SPEC CPU2006 license agreement does not allow you to post the above file on any public ftp server. If your institution has a SPEC CPU2006 license, then it's fine to post it on an internal server that is accessible only to members of your institution.
Next, you are going to retrieve specbzip2.exe, specmd5sum.exe, and spectar.exe from the DVD.
Please do not use Windows Zip utilities, as these will not preserve line endings and will cause difficult-to-diagnose benchmark miscompares.
Please do not use other tar utilities, as these may not handle long path names. Many commonly-supplied tar utilities cannnot.
If you have GNU tar and the genuine bzip2, then you can use those; otherwise, look around on the DVD to find the SPEC-supplied versions, like so:
D:\>cd tools
D:\tools>cd bin
D:\tools\bin>dir
Volume in drive D is SPEC_CPU2006v103
Volume Serial Number is 8D09-673E
Directory of D:\tools\bin
08/09/2007 03:40 PM <DIR> .
02/21/2007 10:44 PM <DIR> ..
08/29/2007 02:06 PM <DIR> aix5L-ppc
08/29/2007 02:06 PM <DIR> freebsd54-ia32
08/29/2007 02:06 PM <DIR> freebsd60-ia32
10/10/2007 04:07 PM <DIR> hpux-11iv1-parisc
08/29/2007 02:06 PM <DIR> hpux-11iv2-ipf
08/29/2007 02:06 PM <DIR> irix6.5-mips
08/29/2007 02:06 PM <DIR> linux-redhat62-ia32
08/29/2007 02:06 PM <DIR> linux-rhas4r4-ia64
08/29/2007 02:06 PM <DIR> linux-suse101-AMD64
08/29/2007 02:06 PM <DIR> linux-suse101-i386
08/29/2007 02:06 PM <DIR> linux-ydl23-ppc
08/29/2007 02:06 PM <DIR> macosx
08/29/2007 02:06 PM <DIR> macosx-ppc
08/29/2007 02:06 PM <DIR> netbsd21-ia32
08/29/2007 02:06 PM <DIR> openbsd38-ia32
08/29/2007 02:06 PM <DIR> sles9-glibc23-ia64
08/29/2007 02:06 PM <DIR> solaris-sparc
08/29/2007 02:06 PM <DIR> solaris-x86
08/29/2007 02:06 PM <DIR> tru64-alpha
08/29/2007 02:06 PM <DIR> windows-i386
0 File(s) 0 bytes
22 Dir(s) 0 bytes free
D:\tools\bin>cd win*
D:\tools\bin\windows-i386>dir
Volume in drive D is SPEC_CPU2006v103
Volume Serial Number is 8D09-673E
Directory of D:\tools\bin\windows-i386
08/29/2007 02:06 PM <DIR> .
08/09/2007 03:40 PM <DIR> ..
04/26/2007 01:21 PM 11,033,448 cpu2006tools-windows-i386.tar.bz2
08/29/2007 01:57 PM 15 order
04/26/2007 01:21 PM 131,072 specbzip2.exe
04/26/2007 01:21 PM 65,536 specmd5sum.exe
04/26/2007 01:21 PM 189,440 spectar.exe
5 File(s) 11,419,511 bytes
2 Dir(s) 0 bytes free
Once you've found these versions of specbzip2, specmd5sum, and spectar, transfer them to system B using the same methods that you used for the big tarfile.
On system B, use specmd5sum to check that the file transfer worked correctly. In this example, we assume that you have placed all 5 of the files mentioned above in the \kits\ directory on drive C::
C:\kits\> specmd5sum -c cpu2006.tar.bz2.md5 cpu2006.tar.bz2: OK
Pick a disk with 8GB free, go there, and unpack the tarfile, like so:
C:\kits\> H: H:\> mkdir cpu2006 H:\> cd cpu2006 H:\cpu2006\> C:\kits\specbzip2 -dc C:\kits\cpu2006.tar.bz2 | C:\kits\spectar -xf -
Be patient: it will take bit of time to unpack! It might take 15 minutes, depending on the speed of your processor and disks. Go for a coffee break.
Now, type install, without any arguments afterwards. That is, unlike the instructions in step 6 above, you do not need to mention a device or directory if you are installing from the tarfile. You will see output similar, though not identical, to that shown in the example installation -- the messages about Unpacking xxxx are not printed, because you already did the unpacking with your spectar command.
Continue with step 7, above.
Copyright (C) 1999-2008 Standard Performance Evaluation Corporation
All Rights Reserved