public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/49032] -gstabs generates reference to deleted static variable
Date: Thu, 19 May 2011 17:28:00 -0000	[thread overview]
Message-ID: <bug-49032-4-gqxiLpGTNa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49032-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49032

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-19 17:07:35 UTC ---
Created attachment 24293
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24293
gcc47-pr49032.patch

Untested fix.  Works on this testcase, as well as when s is actually forced to
be output (e.g. through inline asm).  I'm not a stabs user (are there any left
anyway?), so don't know whether it doesn't decrease debug info quality (if we
can speak about debug info quality in stabs case), but from I understand at
least the global_decl debug hooks are called at least by C/C++ FEs after
cgraph_finalize_compilation_unit has been called and thus IMHO the patch should
only change anything when the vars aren't output.
Guess one could put there instead gcc_unreachable (); instead of return NULL;
and see how often it triggers during -gstabs bootstrap.


  reply	other threads:[~2011-05-19 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 19:43 [Bug debug/49032] New: " arthur.j.odwyer at gmail dot com
2011-05-19 17:28 ` jakub at gcc dot gnu.org [this message]
2011-05-23 18:25 ` [Bug debug/49032] " jakub at gcc dot gnu.org
2011-05-23 18:45 ` jakub at gcc dot gnu.org
2011-05-23 18:50 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-49032-4-gqxiLpGTNa@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).