summaryrefslogtreecommitdiff
path: root/doc/gmp.texi
diff options
context:
space:
mode:
authorTorbjorn Granlund <tege@gmplib.org>2011-04-28 21:14:58 +0200
committerTorbjorn Granlund <tege@gmplib.org>2011-04-28 21:14:58 +0200
commit170630e8577dc2df1a9f0ede09fa874c805c4a6b (patch)
treeb5e76829619529ee05aee14a8a6f7e419f58c718 /doc/gmp.texi
parent3d76d4643bf048a9b9f6062eff63e889bd669491 (diff)
downloadgmp-170630e8577dc2df1a9f0ede09fa874c805c4a6b.tar.gz
Mention benign out-of-bounds read in Valgrind context.
Diffstat (limited to 'doc/gmp.texi')
-rw-r--r--doc/gmp.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/gmp.texi b/doc/gmp.texi
index 425e69578..67fb5c4ac 100644
--- a/doc/gmp.texi
+++ b/doc/gmp.texi
@@ -2657,6 +2657,11 @@ Recent versions of Valgrind are getting support for MMX and SSE/SSE2
instructions, for past versions GMP will need to be configured not to use
those, ie.@: for an x86 without them (for instance plain @samp{i486}).
+GMP's assembly code sometimes promotes a read of the limbs to some larger size,
+for efficiency. GMP will do this even at the start and end of a multilimb
+operand, using naturaly aligned operations on the larger type. This may lead
+to benign reads outside of allocated areas, triggering complants from Valgrind.
+
@item Other Problems
Any suspected bug in GMP itself should be isolated to make sure it's not an
application problem, see @ref{Reporting Bugs}.