Added note about Cachegrind's hack treatment of 28/108B FPU instrs to

shortcomings list in manual.

git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_1_0_BRANCH@862

diff --git a/docs/manual.html b/docs/manual.html
index 47ec6221cd361a09fe1937b84a4ca0e9076b669a..bb95561ca472952b100b579d35b7e8258f0d7650 100644 (file)
--- a/docs/manual.html
+++ b/docs/manual.html
@@ -2677,6 +2677,13 @@ Valgrind's cache profiling has a number of shortcomings:
       <blockquote><code>btsl %eax, %edx</code></blockquote>
 
       This should only happen rarely.
+      </li><p>
+
+  <li>FPU instructions with data sizes of 28 and 108 bytes (e.g.
+      <code>fsave</code>) are treated as though they only access 16 bytes.
+      These instructions seem to be rare so hopefully this won't affect
+      accuracy much.
+      </li><p>
 </ul>
 
 Another thing worth nothing is that results are very sensitive.  Changing the