document in NEWS the fact that stack registration start/end boundaries

are the lowest/highest addressable bytes

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14393

diff --git a/NEWS b/NEWS
index d775d768cf1e774a588322670969e74bf9953930..7604df9a238844f36dd33e86d211d5e4fa310319 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -45,6 +45,11 @@ Release 3.10.0 (?? ?????? 201?)
 
 * ==================== OTHER CHANGES ====================
 
+* The semantic of stack start/end boundaries in valgrind.h
+  VALGRIND_STACK_REGISTER has been clarified/documented.
+  The convention is that start and end are respectively the lowest
+  and highest addressable bytes of the stack.
+
 * Better stacktraces and suppression matching for inlined function calls.
   The new option --read-inline-info=yes|no allows to control the reading
   of the dwarf debug information describing inlined function calls.