On Wed, Nov 19, 2014 at 11:46 AM, David Malcolm <[email protected]> wrote:
> Valgrind complains about uninitialized data within sparseset_bit_p.
> Provide a suppression file to silence these warnings.
>
> Valgrind requires suppression files for C++ code to use the mangled
> names, so we do that here.
There is --enable-valgrind-annotations to get the same effect by GCC
telling valgrind about this (and more).
Richard.
> contrib/ChangeLog
> PR jit/63854
> * valgrind.supp: New.
> ---
> contrib/valgrind.supp | 11 +++++++++++
> 1 file changed, 11 insertions(+)
> create mode 100644 contrib/valgrind.supp
>
> diff --git a/contrib/valgrind.supp b/contrib/valgrind.supp
> new file mode 100644
> index 0000000..ec9ff02
> --- /dev/null
> +++ b/contrib/valgrind.supp
> @@ -0,0 +1,11 @@
> +{
> + suppress-uninit-cond-with-sparseset_bit_p
> + Memcheck:Cond
> + fun:_ZL15sparseset_bit_pP13sparseset_defm
> +}
> +
> +{
> + suppress-uninit-use-with-sparseset_bit_p
> + Memcheck:Value8
> + fun:_ZL15sparseset_bit_pP13sparseset_defm
> +}
> --
> 1.8.5.3
>
