From: Jakub Jelinek <jakub@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, patches@linaro.org,
richard.sandiford@linaro.org
Subject: Re: [2/2] Reducing the overhead of dwarf2 location tracking
Date: Fri, 04 Mar 2011 14:50:00 -0000 [thread overview]
Message-ID: <20110304144954.GE30899@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <AANLkTi=fnEdfJoaMfvQmtmHYeUmecAuck5K=TGE+Xx-T@mail.gmail.com>
On Fri, Mar 04, 2011 at 03:30:34PM +0100, Richard Guenther wrote:
> On Fri, Mar 4, 2011 at 2:56 PM, Richard Sandiford
> > Jakub confirms that this indeed the intended behaviour, and I haven't
> > seen any problem with the output.
>
> Hm, but isn't it incorrect debug info? I would have expected this
> non-localized var to be the abstract origin of a copy for location
> list purposes.
I thought we've discussed that on IRC. For -fcompare-debug reasons
the decision on what decl is localized and what goes into
BLOCK_NONLOCALIZED_VARS can't take into account debug stmts (otherwise
there would be -fcompare-debug failures).
Thus, we sometimes decide to have some BLOCK_NONLOCALIZED_VARS vars
referenced in debug stmts.
The way this works is we do normal var-tracking against those, and then
at dwarf2out.c time just pick their locations up.
See e.g.
http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00445.html
for some of the details.
Jakub
next prev parent reply other threads:[~2011-03-04 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 13:57 Richard Sandiford
2011-03-04 14:30 ` Richard Guenther
2011-03-04 14:47 ` Richard Sandiford
2011-03-04 14:50 ` Jakub Jelinek [this message]
2011-03-04 15:00 ` Richard Guenther
2011-03-04 15:10 ` Jakub Jelinek
2011-03-04 15:15 ` Richard Guenther
2011-03-04 15:48 ` Richard Sandiford
2011-03-04 15:22 ` Jakub Jelinek
2011-03-05 14:38 ` Richard Sandiford
2011-03-28 9:00 ` Matthias Klose
2011-04-04 10:50 ` Richard Sandiford
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=20110304144954.GE30899@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=patches@linaro.org \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@linaro.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).