On Thu, Apr 13, 2023 at 07:39:01AM +0000, Richard Biener wrote:
> On Thu, 13 Apr 2023, Jiufu Guo wrote:
> I think this should be fixed in the analyzer, "stripping" malloc
> tracking from fopen/fclose since it does this manually. I've adjusted
> the bug accordingly.
Yeah.
> > > +/* This case checks double-fclose only, suppress other warning. */
> > > +/* { dg-additional-options -Wno-analyzer-double-free } */
So please add "(PR108722)" or such to the comment here? That is enough
for future people to see if this is still necessary, to maybe remove it
from the testcase here, but certainly not cargo-cult it to other
testcases!
Thanks,
Segher
