This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/77692] [7 regression] gcc.dg/debug/dwarf2/const-2b.c FAILs
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 26 Sep 2016 06:41:13 +0000
- Subject: [Bug debug/77692] [7 regression] gcc.dg/debug/dwarf2/const-2b.c FAILs
- Auto-submitted: auto-generated
- References: <bug-77692-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77692
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> So -- is it worth trying to handle this special case where we know a variable
> is readonly by means of nothing referencing it? Then the following fixes it:
It is certainly worth it, at least as long as the initializer isn't huge (but
that is dwarf2out.c business to decide that). Even if the variable is
optimized out, people might want to ask about its value in the debugger (and
often do).