Hello,
from time to time, I come upon a testcase that failed during the automated
runs, but passes during reduction; there are valgrind warnings present,
however. How do I distinguish what warnings are valid and which are false
positives? Is there any way gcc could prevent generating the false
p
Hello Paul,
(sorry for re-post, I didn't include the ML in the original reply)
-- Původní e-mail --
Od: Paul Floyd via Gcc
Komu: gcc@gcc.gnu.org
Datum: 24. 11. 2021 20:16:33
Předmět: Re: distinguishing gcc compilation valgrind false positives
"
On 24/11/2021 20:05, Zd
Hello Jeff,
-- Původní e-mail --
Od: Jeff Law via Gcc
Komu: Paul Floyd , gcc@gcc.gnu.org
Datum: 24. 11. 2021 20:33:02
Předmět: Re: distinguishing gcc compilation valgrind false positives
"
On 11/24/2021 12:15 PM, Paul Floyd via Gcc wrote:
>
> On 24/11/2021 20:05, Z
Hello Jan,
-- Původní e-mail --
Od: Jan Hubicka via Gcc
Komu: Martin Jambor
Datum: 25. 11. 2021 11:13:33
Předmět: Re: distinguishing gcc compilation valgrind false positives
> >
> > diff --git a/gcc/ipa-prop.h b/gcc/ipa-prop.h
> > index 42842d9466a..1d0c115465c 100644
>
Hello Jan,
-- Původní e-mail --
Od: Jan Hubicka
Komu: Zdenek Sojka
Datum: 25. 11. 2021 12:54:00
Předmět: Re: distinguishing gcc compilation valgrind false positives
>
> I can confirm that zero-initializing node_is_self_scc prevents the
> uninitialised use warnings in inco
