https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
frankhb1989 at gmail dot com changed:
What|Removed |Added
CC||frankhb1989 at gmail dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #6 from lh_mouse ---
(In reply to Markus Trippelsdorf from comment #5)
> (In reply to lh_mouse from comment #4)
> > (In reply to Jonathan Wakely from comment #3)
> > > OK, whatever weird definition of leak you are using is irrelevant.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #4 from lh_mouse ---
(In reply to Jonathan Wakely from comment #3)
> OK, whatever weird definition of leak you are using is irrelevant. The
> memory is still in use until the program exits, and there is still a pointer
> to it. It is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #3 from Jonathan Wakely ---
OK, whatever weird definition of leak you are using is irrelevant. The memory
is still in use until the program exits, and there is still a pointer to it. It
is not lost, or forgotten about, it is in use by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
lh_mouse changed:
What|Removed |Added
CC||lh_mouse at 126 dot com
--- Comment #2 from l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
