Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: tromey@redhat.com, Pedro Alves <pedro@codesourcery.com>,
		gdb-patches@sourceware.org
Subject: Re: [RFA] Use data cache for stack accesses
Date: Thu, 03 Sep 2009 19:45:00 -0000	[thread overview]
Message-ID: <20090903194451.GA8440@caradoc.them.org> (raw)
In-Reply-To: <e394668d0909030838r469b81c7w5e32bcf9cd1dbf9@mail.gmail.com>

On Thu, Sep 03, 2009 at 08:38:30AM -0700, Doug Evans wrote:
> On Wed, Sep 2, 2009 at 1:42 PM, Tom Tromey<tromey@redhat.com> wrote:
> >>>>>> "Doug" == Doug Evans <dje@google.com> writes:
> >
> > Doug> * dwarf2loc.c (dwarf2_evaluate_loc_desc): Mark values on stack with
> > Doug> set_value_stack.
> >
> > I ran across this while merging the DW_OP_*_value patch.
> >
> > Do we really know that such values always come from the stack?  It seems
> > plausible to me that this is the case in practice, but aren't compilers
> > free to refer to any memory at all from a DWARF expression?
> 
> Blech.  It's a bit confusing.
> 
> I don't honestly know.
> I'll do some research.

They can come from the stack, or elsewhere.  You might be able to
track based-on (similar to how prologue-value.h does it) to identify
CFA-relative accesses.  DW_OP_deref has to clear it, though.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2009-09-03 19:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 20:49 Jacob Potter
2009-07-08 20:51 ` Pedro Alves
2009-07-08 20:58   ` Pedro Alves
2009-07-08 23:46   ` Daniel Jacobowitz
2009-07-09  3:06     ` Pedro Alves
2009-07-10  9:34       ` Pedro Alves
2009-07-10  8:45     ` Jacob Potter
2009-07-10 14:19       ` Pedro Alves
2009-07-13 19:25         ` Jacob Potter
2009-08-21  6:25   ` Doug Evans
2009-08-25  3:00     ` Doug Evans
2009-08-25 18:55       ` Pedro Alves
2009-08-26 16:36         ` Doug Evans
2009-08-26 22:45           ` Pedro Alves
2009-08-27  0:46             ` Doug Evans
2009-08-27  3:11               ` Doug Evans
2009-08-29  5:16             ` Doug Evans
2009-08-29 18:28               ` Doug Evans
2009-08-29 20:25               ` Pedro Alves
2009-09-02 20:43       ` Tom Tromey
2009-09-03 15:38         ` Doug Evans
2009-09-03 19:38           ` Tom Tromey
2009-09-03 19:45           ` Daniel Jacobowitz [this message]
2009-07-09 12:20 ` Eli Zaretskii

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=20090903194451.GA8440@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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