public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46724] [4.6 Regression] Wrong debug info: Invalid variable location
Date: Thu, 16 Dec 2010 05:39:00 -0000	[thread overview]
Message-ID: <bug-46724-4-rRHZnpUWne@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46724-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2010-12-16 05:38:44 UTC ---
Considering that we create a decl for the implicit argument that holds the
address of <result>, perhaps the best approach would be to emit debug info for
that artificial decl.  The initial implicit binding of argument variables to
their incoming locations should take care of the debug info for the artificial
parameter throughout the function, and the location of <result> could then be
given in terms of the artificial variable (dwarf calls).  Does that sound
sensible?


  parent reply	other threads:[~2010-12-16  5:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 14:33 [Bug debug/46724] New: " krebbel at gcc dot gnu.org
2010-11-30 14:37 ` [Bug debug/46724] " krebbel at gcc dot gnu.org
2010-11-30 14:48 ` krebbel at gcc dot gnu.org
2010-12-02  9:51 ` [Bug debug/46724] [4.6 Regression] " krebbel at gcc dot gnu.org
2010-12-02 12:11 ` jakub at gcc dot gnu.org
2010-12-16  5:39 ` aoliva at gcc dot gnu.org [this message]
2010-12-17  6:14 ` aoliva at gcc dot gnu.org
2010-12-17  6:19 ` aoliva at gcc dot gnu.org
2010-12-17  8:55 ` jakub at gcc dot gnu.org
2010-12-17  9:44 ` jakub at gcc dot gnu.org
2010-12-18  8:02 ` aoliva at gcc dot gnu.org
2010-12-18  8:05 ` aoliva at gcc dot gnu.org
2010-12-22  3:49 ` aoliva at gcc dot gnu.org
2010-12-22  3:56 ` aoliva at gcc dot gnu.org
2011-01-19 22:08 ` aoliva 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-46724-4-rRHZnpUWne@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).