diff options
author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2015-09-07 09:15:01 +0000 |
---|---|---|
committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2015-09-07 09:15:01 +0000 |
commit | a61bbe8601aac72fd18d038cbe768bf664ce7bc2 (patch) | |
tree | d3530e17d20abbf107f63fe3488085fa7336ce9b | |
parent | 02be18e71873bc4d65f9570c5e0553d05081d004 (diff) | |
download | mpfr-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-- | TODO | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -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"). ############################################################################## |