OpenCores
URL https://opencores.org/ocsvn/openmsp430/openmsp430/trunk

Subversion Repositories openmsp430

[/] [openmsp430/] [trunk/] [core/] [sim/] [rtl_sim/] [src-c/] [dhrystone_v2.1/] [original_files/] [README.RER] - Blame information for rev 145

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 145 olivier.gi
12/04/88
2
 
3
Here is Reinhold Weicker's DHRYSTONE 2.1 benchmark, slightly modified
4
by me for instrumentation purposes only.  This is an integer CPU
5
benchmark.  The differences between 2.0 and 2.1 are minor, and
6
I believe that 2.0 and 2.1 results are comparable.
7
 
8
For purists, I've enclosed context diffs to turn what I'm posting
9
as 2.1 back into what Reinhold sent me as 2.1.  The changes
10
are in pure2_1.dif.  As you can see, it is only the instrumentation
11
that is slightly different.
12
 
13
Both the C and the Pascal versions are here.  The Ada version I
14
have is marked preliminary (not to be posted).
15
 
16
I've enclosed a new submission form (note new address for mailings).
17
Please deluge this mailbox (..!uunet!pcrat!dry2) with your results.
18
I'll summarize and repost when the dust clears.  Please do not
19
assume that I will pull posted results off of the net (I won't, its
20
too much work).
21
 
22
I've attempted to include a Makefile for UNIX and Microsoft C (with ndmake).
23
Pay particular attention to the HZ parameter, even though your power may
24
be 50 or 60 hertz, your computer may not be.  You may have to ask someone,
25
read the manual, or check:
26
        /usr/include/sys/param.h
27
        /usr/include/limits.h           (CLK_TCK==HZ)
28
for this information.
29
 
30
REPEAT: HZ IS NOT NECESSARILY THE FREQUENCY OF YOUR AC POWER !!!!!!
31
 
32
There are two versions to run, one with register variables, and one
33
without.  Please let the benchmark run for 30,000 loops on sixteen
34
bit machines, and for much longer (a minute or two) on faster machines.
35
Please note that "time(2)" has a resolution of 1 second, and may give
36
variable results.  No matter how time is measured, a sanity check with
37
a stopwatch is prudent.  We've run into systems that lie about time,
38
and there is always the configuration error problem.  When it comes
39
to time measurement on UNIX, there is no widely adhered to standard.
40
 
41
For segmented architectures, it is appropriate to submit results for
42
all memory models, as shown below.
43
 
44
I dropped the CODESIZE information that I attempted to add the last
45
time I posted this.  People couldn't follow directions, and the
46
information wasn't very useful anyway.
47
 
48
Here's a sample submission of results:
49
 
50
DHRYSTONE 2.1 BENCHMARK REPORTING FORM
51
MANUF: IBM
52
MODEL: PC/AT
53
PROC: 80286
54
CLOCK: 8
55
OS: Venix
56
OVERSION: SVr2.3
57
COMPILER: AT&T cc
58
CVERSION: 11/8/84
59
OPTIONS: -O
60
NOREG: 1450
61
REG: 1450
62
NOTES: HZ=60; Small Model
63
DATE: 03/04/88
64
SUBMITTER: pcrat!rick (Rick Richardson)
65
MAILTO: uunet!pcrat!dry2
66
 
67
DHRYSTONE 2.1 BENCHMARK REPORTING FORM
68
MANUF: IBM
69
MODEL: PC/AT
70
PROC: 80286
71
CLOCK: 8
72
OS: Venix
73
OVERSION: SVr2.3
74
COMPILER: AT&T cc
75
CVERSION: 11/8/84
76
OPTIONS: -O -Ml
77
NOREG: 1043
78
REG: 1043
79
NOTES: HZ=60; Large Model
80
DATE: 03/04/88
81
SUBMITTER: pcrat!rick (Rick Richardson)
82
MAILTO: uunet!pcrat!dry2
83
 
84
The program that processes submission forms is rather dumb.  Please
85
do not change the order, add or removes lines in the form.  If your
86
NOTES are longer than the space provided, then they are too long for
87
the summary.  Keep it terse, please.
88
 
89
A form consists of all lines between:
90
        DHRYSTONE 2.1 BENCHMARK REPORTING FORM
91
and
92
        MAILTO: uunet!pcrat!dry2
93
both lines must be present for the form to be processed.  If
94
a field does not apply or is not known, leave it blank.  The fields
95
are:
96
        MANUF:  Computer manufacturer, e.g. AT&T, IBM
97
        MODEL:  Model number of computer
98
        PROC:   If a microprocessor CPU, the part number, e.g. 68030
99
        CLOCK:  Clock in Mhz, if known.  Numeric only, e.g. 16.67
100
        OS:     Operating system, e.g. UNIX
101
        OVERSION: OS version, e.g. SVR3
102
        COMPILER: Compiler name, e.g. cc, Microsoft, or Green Hills
103
        CVERSION: Compiler version, e.g. 5.10
104
        OPTIONS: Relevant compiler options, e.g. -O3
105
        NOREG:  Dhrystones/second, no register attribute
106
        REG:    Dhrystones/second, with register attribute
107
        NOTES:  Additional, terse comments on one line
108
        DATE:   Date of test, US format MM/DD/YY
109
        SUBMITTER: uucp or domain address (full name)
110
 
111
 
112
HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ
113
 
114
Please, if you are using times(2) to measure time, indicate
115
the HZ value you used in the NOTES field.  Something like this is OK:
116
 
117
        NOTES: HZ=100; no inlining...
118
 
119
HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ HZ
120
 
121
--
122
                Rick Richardson, President, PC Research, Inc.
123
 
124
(201) 542-3734 (voice, nights)   OR     (201) 389-8963 (voice, days)
125
uunet!pcrat!rick (UUCP)                 rick%pcrat.uucp@uunet.uu.net (INTERNET)
126
                uunet!pcrat!dry2   (Dhrystone submission forms only)

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.