Hi,
Here are two runs for you:
vincent@vincent-panda:~/phrot$ ./phrot -q 10^16384+1
Phil Carmody's Phrot (0.72)
Input 10^16384+1 : Actually testing 10000*1000000^2730+1 (witness=3
2731/6144 limbs)
10^16384+1 is composite LLR64=c5ff6a4a68324d5a. (e=0.01953
(0.0411076~3.737...@0.000) t=81.40s)
vincent@vincent-panda:~/phrot$ ./phrot -q 10^16384+1
Phil Carmody's Phrot (0.72)
Input 10^16384+1 : Actually testing 10000*1000000^2730+1 (witness=3
2731/6144 limbs)
10^16384+1 is composite LLR64=c5ff6a4a68324d5a. (e=0.01953
(0.0411076~3.737...@0.000) t=81.20s)
Best regards,
--
Vincent Stehlé
Systems Engineer - TI France
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve
Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920
But I think I can make it even quicker with some compiler optimization
tuning.
Does GCC use emulated floating
point instructions for default on the A9?
And NEON can not accelerate double precision float work,right?
Could you rerun the test? Thanks!
Link: http://rapidshare.com/files/445466345/phrot_beagle_2.tar.gz
> Thanks! The LLR64 residue is correct,so I can assume that phrot runs
> fine on the Panda too.
> The speed is about 1/4 of that of a 3.2 GHZ P4,which is very good
> considering this benchmark is so floating point intensive.
The P4 is one of the worst micro-architectures in modern times.
Almost anything looks good in comparison. That said, the A9 has a
pretty good floating-point unit.
> But I think I can make it even quicker with some compiler optimization
> tuning.
> The updated file in the link below has compiler optimization flags
> changed from:
> -O3
> to:
> -O3 -march=armv7-a -mcpu=cortex-a9 -mfloat-abi=softfp
> which should give it some speed boost. Does GCC use emulated floating
> point instructions for default on the A9?
The gcc defaults depend on what options were set when it was built.
> And NEON can not accelerate double precision float work,right?
NEON vectors are single-precision (or integer) only. Double-precision
operations are always scalar.
--
Måns Rullgård
ma...@mansr.com
2011/2/1 Måns Rullgård <ma...@mansr.com>: