Open main menu

CDOT Wiki β

Changes

Supporting Architectures above armv5tel

636 bytes added, 20:52, 9 December 2010
Project Plan
Goals for each release:
*<b><font style="font-size:100%"> 0.1 Run a benchmark program specifically designed not to use much 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. 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.
There has been a big focus on arm specific options for gcc recently. In gcc-4.4 the value <code>vfpv3</code> for the <code>-mfpu</code> option was included. More updates are expected for gcc as more and more companies focus their sights on ARM processors.
 
Dhrystone is selected as the benchmark program for this release. Several reasons make Dhrystone a good program to test the general processor performance of the beagleboardXM.
 
<b><font style="font-size:100%">Reasons for using Dhrystone</font></b>
*ARM® recognizes the program and uses it as a performance attribute of their processors.
*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)
 
Test Result:
2
edits