CedarWhetstoneDoc.tioga
Created by Neil Gunther, December 10, 1986 4:25:20 pm PST
Last Edited by: Neil Gunther December 10, 1986 2:56:54 pm PST
CedarWhetstone
CEDAR 6.1 — FOR INTERNAL XEROX USE ONLY
CedarWhetstone
Neil Gunther
© Copyright 1986 Xerox Corporation. All rights reserved.
Abstract: CedarWhetstone is a translation of the famous Whetstone benchmark by H.J. Curnow and B.A. Wichman in Computer Journal 19, No 1, February 1976. It purports to test compiler optimization and exercises the floating-point performance of the processor. The concomitant integer arithmetic benchmark is available in CedarDhrystone.
Created by: Neil Gunther
Maintained by: Neil Gunther <Gunther.pa>
Keywords: Floating-point, Benchmark
XEROX Xerox Corporation
Palo Alto Research Center
3333 Coyote Hill Road
Palo Alto, California 94304
For Internal Xerox Use Only
1. The Whetstone Benchmark
Used to test compiler optimization and floating point performance.
The benchmark consists of an initiating call to the main procedure body, which comprises 11 loops called "Modules" (NOTE: Module 5 is omitted in the C version from which this Cedar translation was taken). Three additional procedures, external to the main procedure, are called during execution. The weighting (number of loop iterations) of each Modules is such that exactly one million "Whetstone instructions" are executed during the timing interval. The metric is Whetstones VIZ., Whetstone instructions per second.
2. The Cedar Implementation
The only significant modification to the benchmark in the Cedar implementation is the declaration of a REF to a real value which is passed as a parameter to procedure p3 in Module 8.
Dorado Whetstones
1 2 3 4
Cedar 606, 960
647, 310
—— ——
1, 3: normal priority (± 50)
2, 4: high priority (± 10)
3, 4: bounds & NIL checking disabled
3. Executing the Benchmark in Cedar
% CedarWhetstone
will load the program and commence execution automatically. All timing is performed internally. In the interest of consistency, no other significant programs should be running at the time the benchmark is performed. The WatchTool is excluded from this caveat since it only consumes about 2% of the cpu.
% FastCedarWhetstone
runs the benchmark as a high priority process.