|Some complaints about SPEC and a request for FORTRAN validation codes email@example.com.EDU (Mayan Moudgill) (1993-03-06)|
|Re: complaints about SPEC and a request for FORTRAN validation codes firstname.lastname@example.org (1993-03-11)|
|Re: complaints about SPEC and a request for FORTRAN validation codes email@example.com (1993-03-11)|
|Re: complaints about SPEC and a request for FORTRAN validation codes grover@brahmand.Eng.Sun.COM (1993-03-12)|
|Re: complaints about SPEC and a request for FORTRAN validation codes firstname.lastname@example.org (1993-03-15)|
|From:||email@example.com (Jeffrey Reilly)|
|Keywords:||benchmarks, Fortran, standards|
|Organization:||Intel Corporation, Santa Clara, CA USA|
|Date:||Thu, 11 Mar 1993 01:10:06 GMT|
firstname.lastname@example.org.EDU (Mayan Moudgill) writes:
>First, a caveat: I've only used the earlier version of SPEC, so I'm not
>sure my comments apply to CFP92.
>Are the FORTRAN programs in SPEC supposed to be Fortran77 compliant? ...
No, the SPEC benchmarks are not guaranteed to be Fortran77 compliant.
>From the SPEC CFP92 Run Rules:
o Source code changes required for standards
compliance should be described in the testing
report. Appropriate standards documents should be
cited. All such changes should be reported to
SPEC. SPEC may consider incorporating such
changes in future releases. Whenever possible,
SPEC will strive to develop and enhance benchmarks
to be POSIX and ANSI compliant.
SPEC's goal was to take existing programs/applications that people use and
develop workloads for them to provide a common reference point for
While a goal of compliance is note-worthy, three points were noticed:
- Making code compliant can be a lot of work (particularly when the authors
of the code are not involved).
- These are benchmarks aimed at measuring CPU performance (not compiler
compliance). It seemed realistic to include non-compliant code in the suite.
- Where is the line drawn at compliance? The goal was to reach the largest
As mentioned in the Run Rules, SPEC is aware of the standards and as
applications and code move toward standard compliance so will the
benchmarks. If you have any input, please let SPEC know.
As mentioned, the SPEC suites were not targeted as a test of compiler
compliance. If the discrepencies with a standard are useful pieces of
information to have or you can provide that, let SPEC know
(email@example.com or firstname.lastname@example.org).
SPEC CINT92/CFP92 Release Manager
Jeff Reilly, Intel Corporation
(408) 765 - 5909
Return to the
Search the comp.compilers archives again.