[Bug tree-optimization/88889] [9 Regression] New valgrind warning since r261039

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88889

--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to jseward from comment #6)
> (In reply to Martin Liška from comment #5)
> > > 
> > > That should make it run clean even without using
> > > --expensive-definedness-checks=yes.  Does it?
> > 
> > Yes, as mentioned in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88889#c2
> 
> Confusion .. #c2 isn't about fixing it without the use of 
> --expensive-definedness-checks=, afaics.

Yes, the valgrind error is gone with --expensive-definedness-checks=yes.