public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: gcc@gcc.gnu.org
Subject: var_tracking question
Date: Fri, 01 Jul 2005 01:26:00 -0000	[thread overview]
Message-ID: <200507010125.j611PlVs019571@greed.delorie.com> (raw)


My m32c port is generating tracking notes that look like this:

(var_location 0x2a95758dd0 (parallel [
            (expr_list:REG_DEP_TRUE (reg/v:SI 0 r0 [orig:123 remainder_size ] [123])
                (const_int 0 [0x0]))
            (expr_list:REG_DEP_TRUE (reg:HI 1 r2 [ remainder_size+2 ])
                (const_int 2 [0x2]))
        ]))

Note that registers are HI natively, and r2 is the upper half of the
[r2:r0] pair.  In other words, the location given above describes an
overlap between the two pieces.  The code itself refers to the
variable in both SI (full) and HI (part) modes.

The dwarf2 location lists generated from this are bogus.

So, my question is - is the var_location correct?  Do I need to debug
the var tracking code, or the dwarf2 output code?

             reply	other threads:[~2005-07-01  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  1:26 DJ Delorie [this message]
2005-07-01  9:50 ` Jakub Jelinek
2005-07-01 14:03   ` Daniel Berlin
2005-07-01 14:13   ` DJ Delorie

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=200507010125.j611PlVs019571@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@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).