On Thu, Apr 14, 2011, maximilian attems wrote: > > BTW, do you have any idea why the build process forces such odd and > > very old toolchain flags instead of just using the defaults? > > (it forces -march=armv4 -mtune=strongarm) > what do you expect currently?
I'd like if klibc would just build with the toolchain defaults, unless there is a reason to diverge; this would provide optimized binaries with exactly the optimization level selected in the toolchain. For instance in Debian armhf and Ubuntu armel, the defaults are armv7-a + thumb-2 which is faster and smaller code. It might also reveal build failures of klibc with these options and call for porting (of course the porters might force the flags to workaround the FTBFS temporarily). Finally, new versions of the ARM architecture have different ways to express certain assembly operations; for instance swp goes away and is replaced by things like strex and ldrex. This might be important in SMP contexts. Another issue with -march=armv4 is that the toolchain is getting worse over time for older CPUs; ARMv4 is getting really old, and I saw some toolchain regressions affecting older CPUs recently, simply because these aren't tested as much. -- Loïc Minier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
