From: Julian Seward Date: Tue, 16 Jul 2002 01:49:22 +0000 (+0000) Subject: Document probs with gcc-3.1 false positives. X-Git-Tag: svn/VALGRIND_1_0_3~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5b87b4d8a7a4faef56bcca6e996641b70fff6e16;p=thirdparty%2Fvalgrind.git 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 c718bca2a5..28fceb752c 100644 --- 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.

+

  • + 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 -fno-builtin-strlen in + the meantime. Or use an earlier gcc.

  • +

    diff --git a/coregrind/docs/manual.html b/coregrind/docs/manual.html index c718bca2a5..28fceb752c 100644 --- 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.

    +

  • + 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 -fno-builtin-strlen in + the meantime. Or use an earlier gcc.

  • +

    diff --git a/docs/manual.html b/docs/manual.html index c718bca2a5..28fceb752c 100644 --- 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.

    +

  • + 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 -fno-builtin-strlen in + the meantime. Or use an earlier gcc.

  • +

    diff --git a/memcheck/docs/manual.html b/memcheck/docs/manual.html index c718bca2a5..28fceb752c 100644 --- 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.

    +

  • + 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 -fno-builtin-strlen in + the meantime. Or use an earlier gcc.

  • +