Open main menu

CDOT Wiki β

Changes

Supporting Architectures above armv5tel

66 bytes removed, 01:01, 10 December 2010
Project Plan
Any packages compiled for the beagleboards can be installed without optimization. So far, in the case of <code>cdot-beagleXM-0-3</code> packages are compiled without it. Without optimizations, software installed in a system can only run on optimal performance. In order to make use of ARMv7 architecture features, editing the <code>CFLAGS</code> to use <code>arm</code> optimization options will let the compiler attempt to improve the performance and/or code size of the program; resulting in a more efficient system.
The goal of this release is to run a benchmark software named [http://en.wikipedia.org/wiki/Dhrystone Dhrystone] and record the results. Three (3) runs are required: '''No optimization''', '''Optimized for armv5tel''', and '''Optimized for armv7'''. The results would answer why the test purpose of running dhrystone is runlisted below:-Check for system performance (optimized vs unoptimized package)-Check if armv7 optimization options and armv5tel optimization options differ significantly in system performance boost-The data gathered can be used as a reference for conducting 0.2 project release.  
<b><font style="font-size:100%">Reasons for using Dhrystone</font></b>
*Dhrystone provides a more meaningful MIPS (Million Instructions Per Second) because results are compared to a reference machine.
*Dhrystone numbers reflect the performance of the C compiler and libraries more so than the performance of the processor itself. (considered as a weakness of the program)
*Check if armv7 optimization options and armv5tel optimization options differ significantly in system performance boost
'''Test Result:'''
*Optimized for armv7 = 1034.82179852 DMIPS
 
The data gathered can be used as a reference for conducting 0.2 project release.
* 0.2
* 0.3
2
edits