[Bug debug/39474] DW_AT_location missing for unused variables even at -O0
--- Comment #5 from jakub at gcc dot gnu dot org 2009-03-17 17:57 --- Fixed. -- jakub at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39474
[Bug debug/39474] DW_AT_location missing for unused variables even at -O0
--- Comment #4 from jakub at gcc dot gnu dot org 2009-03-17 17:53 --- Subject: Bug 39474 Author: jakub Date: Tue Mar 17 17:53:01 2009 New Revision: 144914 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144914 Log: PR debug/39474 * tree-ssa-live.c (remove_unused_locals): Don't remove local unused non-artificial variables when not optimizing. Modified: trunk/gcc/ChangeLog trunk/gcc/tree-ssa-live.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39474
[Bug debug/39474] DW_AT_location missing for unused variables even at -O0
--- Comment #3 from jan dot kratochvil at redhat dot com 2009-03-17 10:03 --- It works for the gdb.python/python-template.exp test, thanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39474
[Bug debug/39474] DW_AT_location missing for unused variables even at -O0
--- Comment #2 from jakub at gcc dot gnu dot org 2009-03-17 09:36 --- Created an attachment (id=17474) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17474&action=view) gcc44-pr39474.patch I disagree. IMHO there is no reason why we should optimize these out at -O0. We don't optimize out already unused global decls at -O0, I think we should treat the local ones the same way. -- jakub at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39474
[Bug debug/39474] DW_AT_location missing for unused variables even at -O0
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-03-16 22:59 --- Well, it doesn't even have a value assigned. So I consider this a valid "optimization" for -O0. Does the variable have a location once you inintialize it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39474