Changes

<font style== "font-size:90%">This Page serves as a guide for running Dhrystone benchmark on arm machines :: Please visit the [http://zenit.senecac.on.ca/wiki/index.php/Supporting_Architectures_above_armv5tel Main Project Name Page] </font>=About Dhrystone=How to compile and optimize Dhrystone for arm machines<font style="font-size:90%">From Wikipedia, the free encyclopedia</font>

Description should be no longer than The name "Dhrystone" is a paragraph. Include links to any relevant pun on-line resources. For example, http://google.com or [http://developer.mozilla.org MDC]a different benchmark algorithm called Whetstone.

== Project LeaderWith Dhrystone, Weicker gathered meta-data from a broad range of software, including programs written in FORTRAN, PL/1, SAL, ALGOL 68, and Pascal. He then characterized these programs in terms of various common constructs: procedure calls, pointer indirections, assignments, etc. From this he wrote the Dhrystone benchmark to correspond to a representative mix. Dhrystone was published in Ada, with the C version for Unix developed by Rick Richardson (s"version 1.1") ==greatly contributing to its popularity.

NameThe Dhrystone benchmark contains no floating point operations, thus the name is a pun on the then-popular Whetstone benchmark for floating point operations. The output from the benchmark is the number of Dhrystones per second (s) the number of iterations of primary people working on the project. If you want to join a project as leader, discuss with other leaders firstmain code loop per second). Include links to personal pages within wiki

Both Whetstone and Dhrystone are synthetic benchmarks, meaning that they are simple programs that are carefully designed to statistically mimic the processor usage of some common set of programs. Whetstone, developed in 1972, originally strove to mimic typical Algol 60 programs based on measurements from 1970, but eventually became most popular in its Fortran version, reflecting the highly numerical orientation of computing in the 1960s.== Project Contributor(s) Dhrystone Fundamentals ==<font style="font-size:90%">From ARM White Paper</font><br />

Name(s) Dhrystone has a number of people casually working on attributes that have led to it being widely used in the projectpast as ameasure of CPU performance.Foremost, or who have contributed significant helpDhrystone is compact, widely available in the public domain, and simple torun. Include links Significantly, there are no lengthy certification processes to personal pages within wikigo through before citingDhrystone figures.Dhrystone compares the performance of the processor under benchmark to that of areference machine. This is an advantage over quoting ‘straight’ MIPS numbers sinceusing a reference machine effectively compensates for differences in the richness ofcompeting instruction sets. For example, literal comparison of the ‘millions ofinstructions per second’ numbers for a RISC architecture and a CISC architecture is notmeaningful.

NOTE: only Project Leader(s) The industry has adopted the VAX 11/780 as the reference 1 MIP machine. The VAX11/780 achieves 1757 Dhrystones per second. The Dhrystone figure is calculated bymeasuring the number of Dhrystones per second for the system, and dividing that by1757. So "80 MIPS" means "80 Dhrystone VAX MIPS", which means 80 times fasterthan a VAX 11/780. A DMIPS/MHz rating takes this normalization process one stepfurther, enabling comparison of processor performance at different clock rates.For all of these reasons, in the past, Dhrystone has been a widely quoted benchmarkfigure. In theory, Dhrystone should add names here. You '''can’t''' add your own name to provide a basis for the Contributor listcomparison of processorperformances.

Provides more depth than the Project Description== What Dhrystone really does ==<font style="font-size:90%">From Clarify. This is the place for technical discussions, project specs, or other detailsdoc (Included in Dhrystone 2. If this gets very long1), you might consider breaking this part into multiple pages and linking to them.Rick Richardson</font><br />

Goals for each release:* 0 <li>DHRYSTONE does not use floating point.1* 0 Typical programs don't.2* 0.3</li>

This is where your regular updates will go <li>DHRYSTONE does not contain much code that can be optimized by vector processors. In these you should discuss the status or your workThat is why a CRAY doesn't look real fast, your interactions with other members they weren't built to do this sort of the community (e.g., Seneca and Mozilla), problems you have encountered, etccomputing.</li>

Put detailed technical information into <li>DHRYSTONE does not measure OS performance, as it avoids calling the O.S. The O.S. is indicated in the results only to help in identifying the compiler technology.</li>  <li>DHRYSTONE is not perfect, but is a hell of a lot better than the "sieve", or "SI".</li>  <li>DHRYSTONE gives results in dhrystones/second. Bigger numbers are better. As a baseline, the Project Details page original IBM PC gives around 300-400 dhrystones/second with a good compiler. The fastest machines today are approaching 100,000.</li> </ul> <font style="font-size:110%"><b>Dhrystone Characteristics</b></font><blockquote><b>Strengths</b><ul><li>Written in C language Code (iAllows code portability)</li><li>Small in size (An easy to understand program)</li><li>Single easy to report score (DMIPS which uses a reference VAX MIPS)</li><li>Potentially useful for 8 and 16-bit microcontroller benchmark</li></ul><b>Weaknesses</b><ul><li>Cannot hope to mimic thebreadth of applications encountered by aprocessor-based system</li><li>Dhrystone only measures a fewmathematical and basic operations</li><li>Does not measure multiply-accumulate, floating-point, SIMD, or anyother type of operations</li><li> Dhrystone’s execution islargely spent in standard C library functions,such as strcmp(),strcpy(), andmemcpy().eCompiler vendors generallyprovide these libraries that are typicallyoptimized and hand-written in assemblylanguage.While you may think you arebenchmarking a processor, update you are reallybenchmarking are the compiler writer’soptimizations of the C library functions for aparticular platform</li></ul></blockquote> = Installation =<font style="font-size:110%"><b>1. Obtaining the Source Code</b></font> One of the most important defects in Dhrystone is that it as you gois often unclear what versionis being quoted. Furthermore, since there are no "disclosure rules" or independentcertification of scores, companies and individuals are free to state, or not state, anything. Due to its non proprietary nature, individuals and companies modified their own versions of Dhrystone resulting in various alterations of the original source code.  The following package is the most quoted, well used Dhrystone release. It is the cleanest/customisable Dhrystone out in the internet.  [http://www.sfr-fresh.com/unix/privat/old/dhrystone-2.1.tar.gz/ Dhrystone-2.1.tar.gz] <font style="font-size:110%"><b>2. Extract the file</b></font> Extract the tarball using the command: <pre>tar xvf dhrystone-2.1.tar.gz -C destination_directory/</pre>There will be a total of 19 files once extracted. Move to the directory where the extracted files are. <font style="font-size:110%"><b>3. Edit the Makefile</b></font> Open Makefile with any text editor; '''UNCOMMENT''' (if commented) then '''EDIT''' the following fields using the '''GIVEN''' values:<blockquote>Line #25 Fedora uses -DTIME for TIME function, this field is commented out by default<pre>TIME_FUNC= -DTIME # Use times(2) for measurement</pre>Line #28Check motherboard specifications to determine the memory clock speed ( beagleboardXM runs at 166MHz DDR speed )<pre>HZ= 166 # Frequency of times(2) clock ticks</pre>Line #39This option is for C compiler<pre>OPTIMIZE= -O2 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fomit-frame-pointer # Optimization Level (generic UNIX)</pre>Line #40This option is for GCC compiler<pre>GCCOPTIM= -O2 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fomit-frame-pointer</pre></blockquote> Comment out/disable the following lines:<blockquote>Line #26 <pre>TIME_FUNC= -DTIMES # Use times(2)for measurement</pre>Line #38<pre>OPTIMIZE= -Ox -G2 # Optimization Level (MSC, 80286)</pre></blockquote> <font style="font-size:110%"><b>Makefile snapshot</b></font>[[Image:Dhry21.png|center]]  <font style="font-size:110%"><b>Compiler Optimization Options</b></font> <font style="font-size:90%">Please see more about [http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html GCC ARM-Options]</font> The options used for lines #39~40 are for optimizing the dhrystone install to run specifically with '''armv7''' architecture. Optimizations provide a performance boost for the program. Removing the optimizations would result in a ''nominal'' program performance. <font style="font-size:110%"><b>4. Run "make"</b></font> Running make in the current directory should only produce warnings!! Here is an output of the make command with warnings relating to c library functions that can be ignored. <blockquote><pre>[mjeamiguel@cdot-beagleXM-0-3 dhrystone]$ makegcc -O2 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fomit-frame-pointer -DTIME -DHZ=166 dhry_1.c dhry_2.c -o gcc_dry2dhry_1.c:31: warning: conflicting types for built-in function ‘malloc’dhry_1.c: In function ‘main’:dhry_1.c:98: warning: incompatible implicit declaration of built-in function ‘strcpy’gcc -O2 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fomit-frame-pointer -DTIME -DHZ=166 -DREG=register dhry_1.c dhry_2.c -o gcc_dry2regdhry_1.c:31: warning: conflicting types for built-in function ‘malloc’dhry_1.c: In function ‘main’:dhry_1.c:98: warning: incompatible implicit declaration of built-in function ‘strcpy’</pre></blockquote> = Running the benchmark and save gathering results = The make command outputs 2 files named '''gcc_dry2''' and '''gcc_dry2reg'''. The author of this section version decided to create 2 dhrystone executables . One with register variables, and one without. Either one will work for the benchmark so, feel free to test it out.  <font style="font-size:110%><b>1. Run the executable by typing ''./gcc_dry2''</b></font> The program will start to ask you for news a ''number of runs''. By convention on newer machines (>=1GHz), the number of runs used is about participation in '''~100000000''' (100 million). There are no rules or standards about how many runs it should be. Some people calculate the number of runs through "Dhrystone run time erros" (way too advanced); what matters is the consistency of the result. For consistent results, dhrystone is executed more than 5 times with same values for number of runs.  <font style="font-size:110%><b>2. Calculate for DMIPS</b></font> One common representation of the Dhrystone benchmark is DMIPS. DMIPS (Dhrystone MIPS ). It is obtained when the Dhrystone score is divided by '''1757''' (the number of Dhrystones per second obtained on the VAX 11/780, nominally a 1 MIPS machine). Given the result: <blockquote><code>Microseconds for one run through Dhrystone: 0.8<br />Dhrystones per Second: 1333333.4</code></blockquote>  Using the formula: '''1333333.4 / 1757 = 758.87''' ''DMIPS''  The result shown was an actual test for a beagleboardXM machine with 1GHz of processor speed. = And... = <font style="font-size:90%">From ARM White paper</font><br /> "When first released, the projectDhrystone benchmark fulfilled a useful function – at least it gave an alternative indicator to vendors’ literal MIPS ratings. However, more than twenty years later, there are undoubtedly better benchmarks available for measuring processor performance."