SPEC logo

SPEC CPU2000: Changes in V1.2

Last updated: 30-Oct-2001 jh

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

New systems supported

With this release of SPEC CPU2000, new support is added for:

Note: links to SPEC CPU2000 documents on this web page assume that you are reading the page from a directory that also contains the other SPEC CPU2000 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:

  • www.spec.org/cpu2000/docs/
  • The $SPEC/docs/ directory on a Unix system where SPEC CPU2000 has been installed.
  • The %spec%\docs.nt\ directory on a Windows/NT system where SPEC CPU2000 has been installed.
  • The docs/ or docs.nt\ directory on your SPEC CPU2000 distribution cdrom.

Documentation Updates

Many of the documents have been moved to HTML format, in hopes that this will make them both easier to read and easier to navigate through. The HTML-format documents include:

Run rule updates

Several run rules have been newly adopted or clarified, including a rule on Fair Use. For additional details, see the Edit History at the top of runrules.html.

Tools updates

The tools make several attempts to record additional information to log files and build directories, for example logging elapsed compile time even if the compile fails, logging the build type (base or peak), and logging the use of src.alt directories.

Changes to benchmarks

In addition to the Windows Advanced Server changes mentioned above, the following benchmark changes were made in V1.2:

Tools new features

Two new styles of line continuation are now supported in config files: line can be continued with either a single backslash (\) or with a double backslash (\\).

The following example illustrates both features:

    OPTIMIZE = -verbose -feedback=compile_time \\
    notes100 = \\
       Crafty is compiled with both the compile-time  \
       feedback option and the aggressive optmization \

The above example creates a single line for OPTIMIZE, with all three switches (-verbose, -feedback, -optimize_level). Also in the example, notes100 is defined as three lines of text.