[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gmp-commit
Subject:    [Gmp-commit] /var/hg/gmp: Fix tyops in last change.
From:       mercurial () gmplib ! org (mercurial at gmplib ! org)
Date:       2013-02-28 12:51:42
Message-ID: hg.af4ce4cd36a9.1362055902.4753027791226180404 () gmplib-02 ! nada ! kth ! se
[Download RAW message or body]

details:   /var/hg/gmp/rev/af4ce4cd36a9
changeset: 15504:af4ce4cd36a9
user:      Torbjorn Granlund <tege at gmplib.org>
date:      Thu Feb 28 13:51:37 2013 +0100
description:
Fix tyops in last change.

diffstat:

 doc/gmp.texi |  9 ++++-----
 1 files changed, 4 insertions(+), 5 deletions(-)

diffs (22 lines):

diff -r f661d334106c -r af4ce4cd36a9 doc/gmp.texi
--- a/doc/gmp.texi	Thu Feb 28 12:00:45 2013 +0100
+++ b/doc/gmp.texi	Thu Feb 28 13:51:37 2013 +0100
@@ -2653,14 +2653,13 @@
 accesses through bad pointers, and memory leaks.
 
 Valgrind does not always support every possible instruction, in particular
-ones recently added to an ISA.  Valgrind might make therefore be incompatible
-with a recent GMP or even a less recent GMP which is compiled using a recent
-GCC.
+ones recently added to an ISA.  Valgrind might therefore be incompatible with
+a recent GMP or even a less recent GMP which is compiled using a recent GCC.
 
 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.
+operand, using naturally aligned operations on the larger type.  This may lead
+to benign reads outside of allocated areas, triggering complaints from Valgrind.
 Valgrind's option @samp{--partial-loads-ok=yes} should help.
 
 @item Other Problems

[prev in list] [next in list] [prev in thread] [next in thread]