https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104076
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's probably just gone latent indeed. I think to give a good false positive
vs. false negative rate we should exclude equality compares from being
considered
as "uses" of a dangling pointer. Note with optimization enabled the errorneous
path doesn't appear anymore (in the second instance of the warning).
