Added note about bts/btr/btc causing bogus cache read counts.

Added to todo list note about files with > 65536 lines.

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

diff --git a/cachegrind/docs/manual.html b/cachegrind/docs/manual.html
index a97c2f9fec2d9ebed2a6f959b80e33f91db6680b..4da22db114816211c389ec81fd95c4efdb6da13a 100644 (file)
--- a/cachegrind/docs/manual.html
+++ b/cachegrind/docs/manual.html
@@ -2374,6 +2374,14 @@ Valgrind's cache profiling has a number of shortcomings:
 
   <li>It doesn't account for cache misses not visible at the instruction level,
       eg. those arising from TLB misses, or speculative execution.</li><p>
+
+  <li>The instructions <code>bts</code>, <code>btr</code> and <code>btc</code>
+      will incorrectly be counted as doing a data read if both the arguments
+      are registers, eg:
+
+      <blockquote><code>btsl %eax, %edx</code></blockquote>
+
+      This should only happen rarely.
 </ul>
 
 Another thing worth nothing is that results are very sensitive.  Changing the
@@ -2394,6 +2402,7 @@ hopefully they should be close enough to be useful.<p>
   <li>Program start-up/shut-down calls a lot of functions that aren't
       interesting and just complicate the output.  Would be nice to exclude
       these somehow.</li><p>
+  <li>Handle files with &gt;65535 lines</li><p>
 </ul> 
 <hr width="100%">
 </body>

diff --git a/coregrind/docs/manual.html b/coregrind/docs/manual.html
index a97c2f9fec2d9ebed2a6f959b80e33f91db6680b..4da22db114816211c389ec81fd95c4efdb6da13a 100644 (file)
--- a/coregrind/docs/manual.html
+++ b/coregrind/docs/manual.html
@@ -2374,6 +2374,14 @@ Valgrind's cache profiling has a number of shortcomings:
 
   <li>It doesn't account for cache misses not visible at the instruction level,
       eg. those arising from TLB misses, or speculative execution.</li><p>
+
+  <li>The instructions <code>bts</code>, <code>btr</code> and <code>btc</code>
+      will incorrectly be counted as doing a data read if both the arguments
+      are registers, eg:
+
+      <blockquote><code>btsl %eax, %edx</code></blockquote>
+
+      This should only happen rarely.
 </ul>
 
 Another thing worth nothing is that results are very sensitive.  Changing the
@@ -2394,6 +2402,7 @@ hopefully they should be close enough to be useful.<p>
   <li>Program start-up/shut-down calls a lot of functions that aren't
       interesting and just complicate the output.  Would be nice to exclude
       these somehow.</li><p>
+  <li>Handle files with &gt;65535 lines</li><p>
 </ul> 
 <hr width="100%">
 </body>

diff --git a/docs/manual.html b/docs/manual.html
index a97c2f9fec2d9ebed2a6f959b80e33f91db6680b..4da22db114816211c389ec81fd95c4efdb6da13a 100644 (file)
--- a/docs/manual.html
+++ b/docs/manual.html
@@ -2374,6 +2374,14 @@ Valgrind's cache profiling has a number of shortcomings:
 
   <li>It doesn't account for cache misses not visible at the instruction level,
       eg. those arising from TLB misses, or speculative execution.</li><p>
+
+  <li>The instructions <code>bts</code>, <code>btr</code> and <code>btc</code>
+      will incorrectly be counted as doing a data read if both the arguments
+      are registers, eg:
+
+      <blockquote><code>btsl %eax, %edx</code></blockquote>
+
+      This should only happen rarely.
 </ul>
 
 Another thing worth nothing is that results are very sensitive.  Changing the
@@ -2394,6 +2402,7 @@ hopefully they should be close enough to be useful.<p>
   <li>Program start-up/shut-down calls a lot of functions that aren't
       interesting and just complicate the output.  Would be nice to exclude
       these somehow.</li><p>
+  <li>Handle files with &gt;65535 lines</li><p>
 </ul> 
 <hr width="100%">
 </body>

diff --git a/memcheck/docs/manual.html b/memcheck/docs/manual.html
index a97c2f9fec2d9ebed2a6f959b80e33f91db6680b..4da22db114816211c389ec81fd95c4efdb6da13a 100644 (file)
--- a/memcheck/docs/manual.html
+++ b/memcheck/docs/manual.html
@@ -2374,6 +2374,14 @@ Valgrind's cache profiling has a number of shortcomings:
 
   <li>It doesn't account for cache misses not visible at the instruction level,
       eg. those arising from TLB misses, or speculative execution.</li><p>
+
+  <li>The instructions <code>bts</code>, <code>btr</code> and <code>btc</code>
+      will incorrectly be counted as doing a data read if both the arguments
+      are registers, eg:
+
+      <blockquote><code>btsl %eax, %edx</code></blockquote>
+
+      This should only happen rarely.
 </ul>
 
 Another thing worth nothing is that results are very sensitive.  Changing the
@@ -2394,6 +2402,7 @@ hopefully they should be close enough to be useful.<p>
   <li>Program start-up/shut-down calls a lot of functions that aren't
       interesting and just complicate the output.  Would be nice to exclude
       these somehow.</li><p>
+  <li>Handle files with &gt;65535 lines</li><p>
 </ul> 
 <hr width="100%">
 </body>