summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-09-07 09:15:01 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-09-07 09:15:01 +0000
commita61bbe8601aac72fd18d038cbe768bf664ce7bc2 (patch)
treed3530e17d20abbf107f63fe3488085fa7336ce9b
parent02be18e71873bc4d65f9570c5e0553d05081d004 (diff)
downloadmpfr-a61bbe8601aac72fd18d038cbe768bf664ce7bc2.tar.gz
[TODO] Updated mpz_t caching item, suggesting mpz_init2 instead.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@9674 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r--TODO5
1 files changed, 3 insertions, 2 deletions
diff --git a/TODO b/TODO
index e77330319..8ee678629 100644
--- a/TODO
+++ b/TODO
@@ -526,8 +526,9 @@ Table of contents:
and mpz_clear (just at the end). So, the differences in the timings are
very surprising, even with a bad malloc implementation. Or is the reason
due to that due to mpz_t caching, the mpz_t's are preallocated with a
- size that is large enough, thus avoiding internal reallocations in GMP?
- (In such a case, mpz_t caching would not be the solution.)
+ size that is large enough, thus avoiding internal reallocations in GMP
+ (with memory copies)? In such a case, mpz_t caching would not be the
+ solution, but mpz_init2 (see GMP manual, 3.11 "Efficiency").
##############################################################################