From: Alexandre Oliva <aoliva@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Henderson <rth@redhat.com>
Subject: Re: [PR debug/47624] improve value tracking in non-VTA locations
Date: Wed, 13 Jun 2012 08:05:00 -0000 [thread overview]
Message-ID: <orr4tj63na.fsf@livre.localdomain> (raw)
In-Reply-To: <or4nsbr654.fsf@livre.localdomain> (Alexandre Oliva's message of "Sun, 22 Apr 2012 15:08:39 -0300")
On Apr 22, 2012, Alexandre Oliva <aoliva@redhat.com> wrote:
> for gcc/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> PR debug/47624
> * var-tracking.c (loc_exp_dep_pool): New.
> (vt_emit_notes): Create and release the pool.
> (compute_bb_dataflow): Use value-based locations in MO_VAL_SET.
> (emit_notes_in_bb): Likewise.
> (loc_exp_dep_insert): Deal with NOT_ONEPART vars.
> (notify_dependents_of_changed_value): Likewise.
> (notify_dependents_of_resolved_value): Check that NOT_ONEPART
> variables don't have a VAR_LOC_DEP_LST.
> (emit_note_insn_var_location): Expand NOT_ONEPART locs that are
> VALUEs or MEMs of VALUEs.
Ping? http://gcc.gnu.org/ml/gcc-patches/2012-04/msg01320.html
RTH, the patch for PR49888 that you reviewed and approved depends on
this one.
--
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:[~2012-06-13 8:02 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
2012-04-22 18:09 ` Alexandre Oliva
2012-06-13 8:05 ` Alexandre Oliva [this message]
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=orr4tj63na.fsf@livre.localdomain \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
/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).