GMP 6.2.1 Aborting when running tuneup program in one.cold()

Simon Sobisch simonsobisch at
Wed Oct 20 14:33:45 UTC 2021

Thanks for the prompt answer!

Am 20.10.2021 um 16:19 schrieb Torbjörn Granlund:
> When tuneup cannot measure things accurately, it bails out.

That's interesting. Is there any thing I can do to help tuneup measure 
things accurately?

Can you please add that important information (abort of the program is 
no bug, just use the non-optimized version) to the documentation
ideally together with the answer to the related questions
"What should -f NNN" relate to?" and "Should I manually build the 
average" (if this isn't an effect of "not accurately measured")?

 > No bug.

Maybe the tuneup program could also hint this at start (additional to 
the doc change)?

Something like

Try finding optimal parameters for ./mpn/x86_64/skylake/gmp-mparam.h
If this is not possible this program will abort, which is no bug, and 
you should use the untuned version.
Using: CPU cycle counter, supplemented by microsecond getrusage()
speed_precision 10000, speed_unittime 3.34e-10 secs, CPU freq 2992.97 MHz
DEFAULT_MAX_SIZE 1000, fft_max_size 50000


More information about the gmp-bugs mailing list