Errata for SPEC CPU2006

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

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

Contents

Introduction

Open Problem Reports

7. The submit command may fail under Windows

11. Runaway specmake.exe on Windows

17. Notice: Unusable path detected followed by run failure

23. FAILED Windows installation - runspec-test.out has Sequence \k... not terminated

Closed Problem Reports

1. Missing example-advanced.cfg

2. Parallel builds aren't parallel on Windows

3. Reporting of seconds

4. Unexpected message installing on Solaris/x86

5. Incorrect path example in shrc.bat on Microsoft Windows

6. The mailcompress option doesn't work yet

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

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

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

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

13. ERROR(update_config_file) with src.alt.

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

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

16. Individual benchmark selection is not allowed for a reportable run

18. Incorrect spelling: "Evironment" when using preENV

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 tied hashes"

22. Some test or train failures may not be properly reported.

Introduction

This document describes known problems in SPEC CPU2006. The latest version of this document may be found at http://www.spec.org/cpu2006/Docs/errata.html.

If you are looking for the solution to a technical question, you might also want to review the latest version of http://www.spec.org/cpu2006/Docs/faq.html.

SPEC CPU2006 is extensively tested on a wide variety of systems prior to release, including a variety of Unix and Linux systems, and a variety of Windows systems; big-endian and little-endian systems; 32-bit and 64-bit systems. Nevertheless, as with any software product, problems may be found too late in the testing process to be fixed in the release, or may be discovered after release.

If you discover problems that are not listed here or in the FAQ, please report them to SPEC.

About the format of this document:

Notice to maintainers: When updating this document, please do not ever re-use problem numbers.

Open Problem Reports

7. The submit command may fail under Windows

11. Runaway specmake.exe on Windows

17. Notice: Unusable path detected followed by run failure

23. FAILED Windows installation - runspec-test.out has Sequence \k... not terminated

Closed Problem Reports

CLOSED: 1. Missing example-advanced.cfg

CLOSED: 2. Parallel builds aren't parallel on Windows

CLOSED: 3. Reporting of seconds

CLOSED: 4. Unexpected message installing on Solaris/x86

CLOSED: 5. Incorrect path example in shrc.bat on Microsoft Windows

CLOSED: 6. The mailcompress option doesn't work yet

CLOSED: 8. Your vendor has not defined POSIX macro WEXITSTATUS with invalid flags file

CLOSED: 9. Error: corrupt result file; unable to format after failed FDO build

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

CLOSED: 12. Style settings may appear ineffective when formatting results with multiple flags files

CLOSED: 13. ERROR(update_config_file) with src.alt.

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

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

CLOSED: 16. Individual benchmark selection is not allowed for a reportable run

CLOSED: 18. Incorrect spelling: "Evironment" when using preENV

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

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

CLOSED: 21. During installation "Error running runspec tests" due to tie.t not ok 20 "unlocalisation of tied hashes"

CLOSED: 22. Some test or train failures may not be properly reported.


Copyright 2006-2011 Standard Performance Evaluation Corporation

All Rights Reserved