public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/43983]  New: var-tracking needlessly throws away location info for SRAed vars
Date: Tue, 04 May 2010 15:11:00 -0000	[thread overview]
Message-ID: <bug-43983-87@http.gcc.gnu.org/bugzilla/> (raw)

track_expr_p has:
4496  /* If this expression is really a debug alias of some other declaration,
we
4497     don't need to track this expression if the ultimate declaration is
4498     ignored.  */
4499  realdecl = expr;
4500  if (DECL_DEBUG_EXPR_IS_FROM (realdecl) && DECL_DEBUG_EXPR (realdecl))
4501    {
4502      realdecl = DECL_DEBUG_EXPR (realdecl);
4503      /* ??? We don't yet know how to emit DW_OP_piece for variable
4504         that has been SRA'ed.  */
4505      if (!DECL_P (realdecl))
4506        return 0;
4507    }

I'd say if the DECL_DEBUG_EXPR is a COMPONENT_REF, ARRAY_REF etc. from a
reasonably short type, the easiest thing would be just to let var-tracking
track the individual vars and let dwarf2out_var_location assemble them
together.


-- 
           Summary: var-tracking needlessly throws away location info for
                    SRAed vars
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org


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


             reply	other threads:[~2010-05-04 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 15:11 jakub at gcc dot gnu dot org [this message]
2010-05-04 15:13 ` [Bug debug/43983] " jakub at gcc dot gnu dot org
2010-05-05 15:22 ` jakub at gcc dot gnu dot org
2010-05-05 19:07 ` jakub at gcc dot gnu dot org
2010-05-05 20:03 ` rguenth at gcc dot gnu dot org
2010-05-06  8:45 ` jakub at gcc dot gnu dot org
2010-05-13 10:41 ` jakub at gcc dot gnu dot org
2010-05-13 10:53 ` jakub at gcc dot gnu dot 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-43983-87@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).