From: Alexandre Oliva <aoliva@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PR debug/47624] improve value tracking in non-VTA locations
Date: Sat, 04 Jun 2011 10:48:00 -0000 [thread overview]
Message-ID: <ork4d1g9mb.fsf@livre.localdomain> (raw)
In-Reply-To: <orvd0l6u7u.fsf@livre.localdomain> (Alexandre Oliva's message of "Tue, 15 Feb 2011 16:14:29 -0200")
On Feb 15, 2011, Alexandre Oliva <aoliva@redhat.com> wrote:
> VTA only tracks locations of gimple regs, while addressable variables
> still use the old var tracking strategy. This means addressable
> variables, during var-tracking, got locations that were not based on
> VALUEs, which failed immediately in the presence of auto-inc addresses.
> The locations also tended to degrade in other ways, when a register
> holding an address happened to be overwritten at a later point.
> This patch arranges for us to track addresses of these variables as
> VALUEs, and to emit new locations for them when a location whose value
> was used to compute its address changes, fixing the problem.
> The patch was regstrapped on x86_64-linux-gnu and i686-linux-gnu. Ok to
> install?
Ping? Retested on both platforms, unchanged except for fixing the typo
s/deug/debug/ in the ChangeLog entry, that Jakub caught.
http://gcc.gnu.org/ml/gcc-patches/2011-02/msg00981.html
> for gcc/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> PR deug/47624
> * var-tracking.c (add_stores): Add FIXME note.
> (compute_bb_dataflow): Use value-based locations in MO_VAL_SET.
> (emit_notes_in_bb): Likewise.
> (check_changed_vars_4): New.
> (emit_noets_for_changes): Call it.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next prev parent reply other threads:[~2011-06-04 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 18:21 Alexandre Oliva
2011-02-15 19:07 ` Jakub Jelinek
2011-06-04 10:48 ` Alexandre Oliva [this message]
2012-04-22 18:09 ` Alexandre Oliva
2012-06-13 8:05 ` Alexandre Oliva
2012-06-13 19:51 ` Richard Henderson
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=ork4d1g9mb.fsf@livre.localdomain \
--to=aoliva@redhat.com \
--cc=gcc-patches@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).