View Single Post
Old 07-16-2012, 04:21 PM   #18
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Hmm.

bash-4.1$ arm-none-linux-gnueabi-gcc -O3 -march=armv6j -mtune=arm1136jf-s -mfpu=vfp -fomit-frame-pointer -o ffttest-arm radix4fft.c testfft.c testmain.c -lm

Any way to squeeze a bit more performance out of that in terms of compilation?
*Goes and googles things.*

Well -03 from http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html looks to be as good as it gets - I vaguely recall someone posting a nice set of args but that could have been for the K5.

Cheers.

Last edited by twobob; 07-16-2012 at 04:46 PM. Reason: added resolution
twobob is offline   Reply With Quote