Open main menu

CDOT Wiki β

Changes

Supporting Architectures above armv5tel

327 bytes added, 00:47, 10 December 2010
Project Plan
<b><font style="font-size:120%"> 0.1 Optimize and run a benchmark program specifically designed to make use of <code>glibc</code></font></b>
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. 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 is run:-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.
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 data gathered can be used as a reference for conducting 0.2 project release.
'''Test Result:'''
 
[[Image:graph.png|widthpx| ]]
'''Legend:'''
*Normal = 758.869322709 DMIPS *Optimized for armv5tel = 1034.82179852 DMIPS *Optimized for armv7 = 1034.82179852 DMIPS
* 0.2
2
edits