Torbjorn Granlund writes:
> Perhaps 0.4 is a bit too coarse?
Ooops. I meant 0.04.
/nisse
--
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.
___
gmp-devel mailing list
gm
ni...@lysator.liu.se (Niels Möller) writes:
I tried some values, amd I think max_size = 1 (or something a bit
smaller, 5000 or 7000) and step_factor = 0.4 should give reasonable
tuning time. When I run ./tuneup -t here, I get
#define HGCD_REDUCE_THRESHOLD...
sizes 30
ler, 5000 or 7000) and step_factor = 0.4 should give reasonable
tuning time. When I run ./tuneup -t here, I get
#define HGCD_REDUCE_THRESHOLD...
sizes 30 to 9748 total 162 measurements
#define HGCD_REDUCE_THRESHOLD 2205
I'm considering checking in that change.
BTW, it
HGCD_REDUCE_THRESHOLD is almost always 996, please see
<http://gmplib.org/devel/HGCD_REDUCE_THRESHOLD.html>.
I tried adding param.max_size = 1 to tune_hgcd_reduce, and on
shell.gmplib.org I now get 3681. Measurements become very slow, one
might want to set a coarser step fact
