Document probs with gcc-3.1 false positives.

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

diff --git a/cachegrind/docs/manual.html b/cachegrind/docs/manual.html
index c718bca2a58b65a973fd824beac0723b0ecfaa87..28fceb752ca77bc674472aaa794497a478c85544 100644 (file)
--- a/cachegrind/docs/manual.html
+++ b/cachegrind/docs/manual.html
@@ -1818,6 +1818,14 @@ Known platform-specific limitations:
       in the ELF frame constructed by the kernel.  The 2.4.18 in the
       standard Red Hat 7.3 release works fine, though.</li><br>
       <p>
+  <li>
+      Inlining of string functions with gcc-3.1 or above causes a
+      large number of false reports of uninitialised value uses.  I
+      know what the problem is and roughly how to fix it, but I need
+      to devise a reasonably efficient fix.  Try to reduce the
+      optimisation level, or use <code>-fno-builtin-strlen</code> in
+      the meantime.  Or use an earlier gcc.</li><br>
+      <p>
 </ul>
 
 

diff --git a/coregrind/docs/manual.html b/coregrind/docs/manual.html
index c718bca2a58b65a973fd824beac0723b0ecfaa87..28fceb752ca77bc674472aaa794497a478c85544 100644 (file)
--- a/coregrind/docs/manual.html
+++ b/coregrind/docs/manual.html
@@ -1818,6 +1818,14 @@ Known platform-specific limitations:
       in the ELF frame constructed by the kernel.  The 2.4.18 in the
       standard Red Hat 7.3 release works fine, though.</li><br>
       <p>
+  <li>
+      Inlining of string functions with gcc-3.1 or above causes a
+      large number of false reports of uninitialised value uses.  I
+      know what the problem is and roughly how to fix it, but I need
+      to devise a reasonably efficient fix.  Try to reduce the
+      optimisation level, or use <code>-fno-builtin-strlen</code> in
+      the meantime.  Or use an earlier gcc.</li><br>
+      <p>
 </ul>
 
 

diff --git a/docs/manual.html b/docs/manual.html
index c718bca2a58b65a973fd824beac0723b0ecfaa87..28fceb752ca77bc674472aaa794497a478c85544 100644 (file)
--- a/docs/manual.html
+++ b/docs/manual.html
@@ -1818,6 +1818,14 @@ Known platform-specific limitations:
       in the ELF frame constructed by the kernel.  The 2.4.18 in the
       standard Red Hat 7.3 release works fine, though.</li><br>
       <p>
+  <li>
+      Inlining of string functions with gcc-3.1 or above causes a
+      large number of false reports of uninitialised value uses.  I
+      know what the problem is and roughly how to fix it, but I need
+      to devise a reasonably efficient fix.  Try to reduce the
+      optimisation level, or use <code>-fno-builtin-strlen</code> in
+      the meantime.  Or use an earlier gcc.</li><br>
+      <p>
 </ul>
 
 

diff --git a/memcheck/docs/manual.html b/memcheck/docs/manual.html
index c718bca2a58b65a973fd824beac0723b0ecfaa87..28fceb752ca77bc674472aaa794497a478c85544 100644 (file)
--- a/memcheck/docs/manual.html
+++ b/memcheck/docs/manual.html
@@ -1818,6 +1818,14 @@ Known platform-specific limitations:
       in the ELF frame constructed by the kernel.  The 2.4.18 in the
       standard Red Hat 7.3 release works fine, though.</li><br>
       <p>
+  <li>
+      Inlining of string functions with gcc-3.1 or above causes a
+      large number of false reports of uninitialised value uses.  I
+      know what the problem is and roughly how to fix it, but I need
+      to devise a reasonably efficient fix.  Try to reduce the
+      optimisation level, or use <code>-fno-builtin-strlen</code> in
+      the meantime.  Or use an earlier gcc.</li><br>
+      <p>
 </ul>