2
edits
Changes
→[0.2] Install an armv7 glibc and re-run the benchmark using dhrystone
===[0.2] Install an armv7 glibc and re-run the benchmark using dhrystone===
'''Requires:''' <blockquote>[http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=8721 glibc binaries]</blockquote> In order for a successful glibc armv7 build, the file ''/usr/lib/rpm/redhat/rpmrc'' needs edit to use armv7 build options. Using mock; a downloaded glibc source can be rebuilt. Once finished, the binaries can then be installed locally to the system using rpm OR a local yum repository can be created enabling the use of yum.
'''Test Result:'''
The Dhrystone (DMIPS) results never changed. The benchmark brought the same, exact number of DMIPS. Although Dhrystone does make use of C library functions and is assumed that the glibc would have effects on the program; the results proved that upgrading the glibc did not bring what's expected.
It is proven that armv7 and armv5 provide the same level of performance especially when running C library dependent programs. Why is it possible when armv7 is supposed to be faster than armv5tel? One big hint to the question is that the system tested currently is built to use an [http://en.wikipedia.org/wiki/Application_binary_interface ABI] called "softfp". Although beagleboardXM (cortex-a8)supports the "hard floating-point" ABI, The Fedora-ARM currently can't afford to waste time in recompiling the packages to support "hardfp".
ARM Floating point is a pretty big topic, provided are some links to help you understand more.
===[0.3]===
