[Bug debug/58315] [4.8/4.9/5 Regression] Excessive memory use with -g

["jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Generally, if the debug stmts are about different variables/parameters, then
supposedly they really shouldn't be useless, you really might be interested in
knowing at all times especially what this is, in the current inline function,
as well as when doing up in virtual backtraces, otherwise you really can't call
methods in the debugger etc.
If it is about debug stmts for the same variable without intervening other
stmts (so, effectively it is something you couldn't really inspect in the
debuggers), then it is something Alex planned in his papers for the future for
virtual stepping without really moving instruction pointers, but if Alex
doesn't plan to work on that in the near future, perhaps we should guarded by
some option perhaps DCE the for now useless debug stmts.  Similarly, if we
don't DCE debug stmts setting debug temporaries that aren't used by any debug
stmts, we perhaps should.