[Valgrind-developers] valgrind/coregrind/docs

[Nicholas N. <nj...@ca...>]

CVS commit by nethercote: 

Update limitations section: merge some old changes from 2.0.0 branch, and some
new changes that only apply to HEAD.


  M +9 -14     coregrind_core.html   1.20


--- valgrind/coregrind/docs/coregrind_core.html  #1.19:1.20
@@ -1187,11 +1187,6 @@
 
 <ul>
-  <li>No MMX, SSE, SSE2, 3DNow instructions.  If the translator
-      encounters these, Valgrind will simply give up.  It may be
-      possible to add support for them at a later time. Intel added a
-      few instructions such as "cmov" to the integer instruction set
-      on Pentium and later processors, and these are supported.
-      Nevertheless it's safest to think of Valgrind as implementing
-      the 486 instruction set.</li>
+  <li>No support for 3DNow instructions.  If the translator encounters
+      these, Valgrind will simply give up.</li>
       <p>
 
@@ -1215,5 +1210,10 @@
   <li>If your program does its own memory management, rather than
       using malloc/new/free/delete, it should still work, but
-      Valgrind's error checking won't be so effective.</li>
+      Valgrind's error checking won't be so effective.
+      If you describe your program's memory management scheme
+      using "client requests" (Section 3.7 of this manual),
+      valgrind can do better.  Nevertheless, using malloc/new
+      and free/delete is still the best approach.
+      </li>
       <p>
 
@@ -1239,5 +1239,5 @@
       demand.  So it's possible, although unlikely, that a program
       will fall over with a message to that effect.  If this happens,
-      please mail me ALL the details printed out, so I can try and
+      please report ALL the details printed out, so we can try and
       implement the missing feature.</li>
       <p>
@@ -1248,9 +1248,4 @@
       <p>
 
-  <li>You can't Valgrind-ize statically linked binaries.  Valgrind
-      relies on the dynamic-link mechanism to gain control at
-      startup.</li>
-      <p>
-
   <li>Memory consumption of your program is majorly increased whilst
       running under Valgrind.  This is due to the large amount of