Last updated: $Date: 2011-09-07 11:08:21 -0400 (Wed, 07 Sep 2011) $ by $Author: CloyceS $

1. Clarify V1 2 0 Hdi
2. Clarify V1 2 0 2
3. Clarify V1 2 0 3

(To check for possible updates to this document, pleasesee http://www.spec.org/cpu2006/Docs/ )

Contents

I. Introduction

II. Changes to system version requirements

The Version 2.0 ENERGY STAR specification for Computer Servers has been finalized and will take effect on December 16, 2013. Materials related to the revision process are provided below. VVSSCG-SC-2020 v1.2. Clarify any ambiguous or erroneous aspects of the guidelines. AVETMISS Release 8.0 updates as of August 2018 apply from 2019. Sonible smartEQ2 1.2; Klevgrand Knorr v1.0.1; Accusonus ERA Bundle Pro v4.1.10 WiN; Toontrack Alt-Rock EZX v1.0.0 SOUNDBANK; XLN Audio DS-10 Drum Shaper 1.0.5 (Win / macOS).

Spec (PR #322): Clarify CreateVolume: idempotent recovery from errors. Spec (PR #265): Clarify default scalar values tagged as REQUIRED or OPTIONAL. Spec (PR #312): Clarify expectations w/ respect to consistency when paging results of ListXYZ calls. Spec (PR #314, PR #315): Clarify VolumeCapability in CreateVolumeRequest. ESLint v7.10.0 released We just pushed ESLint v7.10.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

A. Linux: a variety of toolsets

B. Unsupported toolsets: BSD dropped; Alpha updated.

III. Benchmark source code changes

IV. Run Rules Changed

V. New and Updated Features

A. New sysinfo

B. Changes to the runspec command

C. Changes to reports Itubedownloader 6 4 5 – video downloader full.

D. Changes to config files

E. Changes to utility programs

F. Changes to log files

G. Changes to flags files

1. Summary of changes

2. Symptoms of old flags files

VI. Problems fixed by SPEC CPU2006 V1.2

Appendix: Open source updates

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:

• The $SPEC/Docs/ (Unix) or %SPEC%Docs (Windows) directory on a system where SPEC CPU2006 has been installed.
• The Docs/ directory on your SPEC CPU2006 distribution DVD.

I. Introduction

SPEC CPU2006 V1.2 is an incremental update to SPEC CPU2006 V1.1. Results generated with SPEC CPU2006 V1.2 are comparableto results from other V1.x releases and vice versa. SPEC CPU2006 V1.2 is intended to improve compatibility, stability,documentation and ease of use. Videosolo video converter ultimate 1 0 30 percent.

If you have already used SPEC CPU2006 V1.0 or V1.1 andalready have configuration files, it is recommended that you read through this document.

Here are the top 3 changes to user-visible behavior that may cause surprises. You should be aware ofthese before using SPEC CPU2006 V1.2:

1. There is a new example sysinfo program, which is enabled by default, and which fills out some of your system information/documentation for the results generated by a run. You may need to adjust your config file.
2. The structure of flags files has changed. If you are doing reportable runs, this change *will* affect your preparation of final disclosures with all required information.
3. specbzip2 has been removed. It is replaced by specxz

There are other changes, including bugfixes, better reporting of sponsors, more flexibility in config files, and much better environment logging. Please read on!

II. Changes to system version requirements

SPEC's toolset was updated and rebuilt for all supported operating systems. See the list of supported platforms in system-requirements.html.

For some (but not all) platforms, the tools rebuild has caused a change to the minimum required level of the OS:

Please ensure that you meet the minimum required version prior to installing SPEC CPU2006 V1.2.

II.A. Linux: a variety of toolsets

There are many Linux distributions. SPEC has made an effort to support a wide variety of them. For details, please seethe Linux table in system-requirements.html.

II.B. Unsupported toolsets: BSD dropped; Alpha updated.

• SPEC CPU2006 V1.1 provided unsupported tools built on BSD. These toolsets are not present in SPEC CPU2006 V1.2.

• SPEC CPU2006 V1.1 provided tools built on Digital Unix V4.0F. For SPEC CPU2006 V1.2, the tools have been rebuilt on Tru64 Unix V5.1B.

Caution:

• Unsupported toolsets are provided as a courtesy, as a service to users who may have the listed platform(s).
• Unsupported toolsets have been tested much less extensively than other tool sets and might or might not work.

• More importantly, some of the benchmarks themselves have not been ported for the environments represented by the unsupported toolsets:

  • Therefore, if you use an unsupported toolset, you will need to dedicate time to a porting effort.
  • Please especially notice that it is impossible to do a reportable run on an unsupported system until such time as SPEC approves any source changes and/or portability flags needed for such system.
  • For more information about obtaining SPEC approval for source changes, see techsupport.html.

III. Benchmark source code changes

The following benchmark changes were made in V1.2:

1. 403.gcc: The input files were renamed to prevent them from being inadvertantly removed by the tools during multi-pass compilation. If you are studying the benchmarks with your own tools, or outside the SPEC tool harness, you may need to adjust your procedures.

2. 447.dealII

   1. Enable compilation with compilers such as Microsoft Visual C++ 2010 that require even unreachable return values to have the correct type, or which require normally implicit casts to be explicit when '0' is an argument to a perfect forwarding function.
   2. Allow compilation with Windows C++ compilers using the EDG 4.0 or later front end (for example PGI 2010)
   3. Enable compilation with the Apache Standard C++ Library

3. 483.xalancbmk

   1. Added portability changes for PGI on Mac OS X
   2. Enable compilation with Microsoft Visual C++ 2010, or with the Apache Standard C++ Library.

IV. Run Rules Changed

Publishable results must adhere to the SPEC CPU2006 Run Rules. In SPEC's opinion, the changes do not affect thecomparabilty of results between SPEC CPU2006 V1.0, V1.1, and V1.2, because the changes are primarily clarifications of theexisting rules.

Here is a list of the rules that have have been changed, excerpted from the change history in runrules.html. (Reminder: as noted above, linksgo to the copy in the same directory as the document you are reading now; the most recent copy is the one atwww.spec.org)

• At the top, clarify that the rules may be updated from time to time.
• In rule 4.2, note that system descriptions may be edited after a test.
• Add rule 4.2.1.1 about identifying equivalent systems.
• In rule 4.2.3, reference the updated mechanism for setting the auto parallel field.
• In rule 4.2.4(g), emphasize that all tuning must be documented.
• In rule 4.2.5 clarify which information belongs in flags files vs. other locations.
• Add rule 4.2.7 on how to document cross compiles, referencing it from 2.0.6.
• Replace rule 4.7 with a reference to the SPEC-wide Fair Use rule.

Regarding the last item above, please note that SPEC has centralized the Fair Use rules for all benchmarks to a singlelocation, for the convenience of those who use SPEC results. The Fair Use rules for all SPECbenchmarks are now posted at a location which is intended to be easily memorable:

V. New and Updated Features

These user-visible features are new, updated, or newly documented for SPEC CPU2006 V1.2:

V.A. New sysinfo

The example sysinfo program is substantially expanded. You can use it toautomatically capture various system configuration items on systems running Linux, Mac OS X, Solaris, and Windows.

Note that the example sysinfo program isenabled by default!

It is on by default because SPEC believes that its virtues outweigh its limitations, both of which are summarized in thissection.

By default, there will be more information in your platform notes. For example, by default Windows systems will includelines such as these:

Also by default, the example sysinfo program will try to parse the above information into system description fields,such as:

Virtues of the example sysinfo program Cinemagraph pro 2 5 1 – create living photoshop.

1. The primary value of a sysinfo program is that it creates a contemporaneous record of the system under test.
2. The record is created under the control of the SPEC toolset.
3. Because system configuration information is automatically recorded, it is not subject to human transcription error.
4. Therefore, the example sysinfo program can remove ambiguity such as 'I remember that I upgraded the version of theoperating system, but I can't quite recall whether that was before or after I did the re-run of the SPECfp2006 test.'
5. The utility works with Windows, Mac OS X, Solaris, and Linux.

It is hoped that users will find it useful that the information is recorded and that some fields are automaticallypopulated, under program control, contemporaneously with your test.

Limitations of the example sysinfo program and likely surprises

1. SPEC is aware that there are many dependencies and differences among hardware and software platforms, and that thesechange from time to time. Therefore, the example sysinfo program is only an 'example': you may need to modify the examplein order to use it on your system.
2. For the same reason, SPEC may decide to update the utility fromtime to time.
3. As of the release of V1.2, the example does not work with other operating systems, such as AIX, IRIX, and HP-UX.

4. You may see WARNINGS when you use it, because the utility is likely towrite fields that are already in your config file:

   If you see warnings such as the above, you will need to decide what to do about them. There are four options suggested inconfig.html.

Details about the sysinfo utility may be found in the config.html section About sysinfo, including how to selectively enable output types, how to resolve conflicting field warnings, and how to write your own sysinfo utility.

V.B. Changes to the runspec command

The --speed option is effective now for runspec, in addition torawformat. A config file containing rate = 1 can therefore be overridden from the commandline, and used for a SPECspeed run by adding --speed to the runspec line. In general, the command line takes precedence over the config file, sothis change makes the switch more compatible with how other switches work.

V.C. Changes to reports

Transfer pictures to computer. If the test sponsor is not the same as the hardware vendor, this fact is now noted more prominently in the generatedHTML, Postscript, and PDF reports.

V.D. Changes to config files

1. The restrictions about placement of certain config file options have been slightly relaxed This change may be of especial interest to users who would like to create macros that write to both the header section and to other config file sections.
2. You can now add tags to all notes, which may allow you to organize your system information in a manner that better suits your own categories for describing it.
3. You can now use += (plus equals) for options that are sent to specmake, an option that increases flexibility. (This feature should be used with caution, as described in the config.html.)
4. The example sysinfo program is called by default.

V.E. Changes to utility programs

1. The program specbzip2 is no longer present. Instead, compression is done via specxz, from XZ Utils 5.0.0. Switching compression programs has reduced the size of SPEC distribution media. If you have written scripts that rely on specbzip2, it will be necessary to either retain a copy of specbzip2 from your V1.1 kit, or to change your scripts to specxz. If you make the change, you will also probably notice that specxz produces smaller files.

   Note that switches commonly used with specbzip2 are also supported by specxz.

2. The specdiff utility now removes prior outputs, thereby eliminating a prior source of confusion.
3. The port_progress utility now allows selective reporting by tuning for convenience during debugging.
4. The printpath utility has been documented. It may help you avoid hard-to-diagose path surprises.
5. The output of specinvoke -nn is expanded to include information about environment variables, which may be very useful when doing runs outside of the SPEC harness for debugging or for tuning.
6. You can also, now, control whether specinvoke continues or exits after individual workload failures. This feature is primarily of interest only during debugging.

V.F. Changes to log files

1. You may notice that the success message has changed to indicate power usage.

   The extra fields are present because the SPEC CPU toolset is used in multiple SPEC benchmarks; measurement of power is not a supported feature in SPEC CPU2006 V1.2. You may ignore these fields.

2. If the preENV feature is used, runspec is restarted with the requested environment change. For SPEC CPU2006 V1.1, the top of the log file had the second, automatically-generated runspec command, and the environment settings were not recorded in the log. Now, with SPEC CPU2006 V1.2, it has the command that the user actually entered, and the settings are logged.

   It is expected that this change will remove a source of confusion, while adding very useful information to the log.

   Example: Consider this simple config file that runs the test workload of 401.bzip2 once, with an environment setting of 32 threads:

   Here is its behavior with SPEC CPU2006 V1.1:

   Here is its behavior with SPEC CPU2006 V1.2:

   Notice above that the runspec command matches what the user entered, and the environment setting is logged. https://galtorrent.mystrikingly.com/blog/sqlpro-studio-1-0-163-powerful-database-manager.

V.G. Changes to flags files

V.G.1. Summary of changes

V.G.2. Symptoms of old flags files

You may realize that you are using an old-format flags file if you see a message similar to this:

The problem above is that although the named file (/cpu2006/V1.2/config/Oracle-Solaris-Studio12.2.xml) has useful information about the tested platform, the information needs to be updated and put into new locations. For SPEC CPU2006 V1.2, instead of using a platform element, you need to use a platform file. The message above is telling you that there is no element named 'platform_settings' (as of V1.2).

An example of how the above error can be resolved is available in flag-description.html.

VI. Problems fixed by SPEC CPU2006 V1.2

Here is a list of the problems have been fixed, excerpted from the table of contents of errata.html. (Reminder: as noted above, links goto the copy in the same directory as the document you are reading now; the most recent copy is the one atwww.spec.org)

8. Your vendor has notdefined POSIX macro WEXITSTATUS with invalid flags file

9. Error: corrupt resultfile; unable to format after failed FDO build

10. WARNING: accessor'benchmark' not found during reportable run

12. Style settings may appear ineffective whenformatting results with multiple flags files

14.WARNING: accessor'setup_error' not found with minimize_rundirs

15. Index utility prints Expected 17 fields; got 16 (base_copies, .

16.Individual benchmarkselection is not allowed for a reportable run

18. Incorrect spelling: 'Evironment' when usingpreENV

19. The config file feature rate=1 is not recommended

20. During installation 'Error running runspec tests' due to time.t 'FAILED at test 2'

21. During installation 'Error running runspec tests' due to tie.t not ok 20 'unlocalisation of tiedhashes'

22. Some test or train failures may not beproperly reported.

Appendix: Open source updates

Clarify V1 2 0 Hdi

The SPEC CPU toolset includes components from many open source programs. Where required by licenses, you will find theoriginal sources, and SPEC's modifications, in this directory:

• $SPEC/redistributable_sources/ (Unix)
• %SPEC%redistributable_sources (Windows), or
• on your SPEC CPU2006 DVD in the directory redistributable_sources/.

Seagate backup plus slim 2tb time machine. Most users have little reason to care about the internal implementation of SPEC's toolset, and if that describes you,feel free to skip this section. It is here for two reasons: (1) If you encounter a problem while using a SPEC-providedtool, it may be useful to know where it came from, and the version thereof. (2) SPEC is thankful to the open sourcecommunity, and gratefully acknowledges the updates that have gone into SPEC CPU2006 V1.2.

For SPEC CPU2006 V1.2, the sources of these tools have been updated:

Newly added are:

• specxz, from XZ Utils 5.0.0, replacing specbzip2
• specsum, extended from md5sum.c of coreutils 8.9 (plus portions of gnulib) replacing the former md5sum 1.1 from textutils.

These perl modules are updated:

Note that any perl modules used in 400.perlbench are not affected. The benchmark has its own copies, set at the releaseof SPEC CPU2006 V1.0, and these modules have not been updated.

These perl modules have been newly added in SPEC CPU2006 V1.2:

• String::ShellQuote 1.04

These (non-perl) modules have been updated:

Clarify V1 2 0 2

These open source modules are unchanged in SPEC CPU2006 V1.2:

• dmake 4.11
• File::NFSLock 1.20
• GD 1.19
• makedepf90 2.8.8
• ntzsh (an early version of what later became WinZsh)

Clarify V1 2 0 3

Copyright 2011 Standard Performance Evaluation Corporation
All Rights Reserved