Re: complaints about SPEC and a request for FORTRAN validation codes

grover@brahmand.Eng.Sun.COM (Vinod Grover)
Fri, 12 Mar 1993 05:51:00 GMT

          From comp.compilers
Related articles
Some complaints about SPEC and a request for FORTRAN validation codes moudgill@cs.cornell.EDU (Mayan Moudgill) (1993-03-06)
Re: complaints about SPEC and a request for FORTRAN validation codes jwreilly@mipos2.intel.com (1993-03-11)
Re: complaints about SPEC and a request for FORTRAN validation codes mash@mash.wpd.sgi.com (1993-03-11)
Re: complaints about SPEC and a request for FORTRAN validation codes grover@brahmand.Eng.Sun.COM (1993-03-12)
What do benchmarks measure? (WAS: complaints about SPEC ...) pardo@cs.washington.edu (1993-03-14)
Re: complaints about SPEC and a request for FORTRAN validation codes jwreilly@mipos2.intel.com (1993-03-15)
| List of all articles for this month |
Newsgroups: comp.benchmarks,comp.compilers
From: grover@brahmand.Eng.Sun.COM (Vinod Grover)
Keywords: benchmarks, Fortran, standards
Organization: Sun
References: 93-03-020 93-03-028
Date: Fri, 12 Mar 1993 05:51:00 GMT

jwreilly@mipos2.intel.com (Jeffrey Reilly) writes:
>- These are benchmarks aimed at measuring CPU performance (not compiler
> compliance).


That is surprising. I thought that SPEC benchmarks were for measuring
*system performance*. For many benchmarks runtimes are dependent on system
features such as malloc (espresso), alloca (gcc), and multiprocessing
(compress), curses libraries (sc). A system having faster versions of
these can skew SPECmarks significantly.


Vinod Grover
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.