This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Use data cache for stack accesses
- From: Doug Evans <dje at google dot com>
- To: tromey at redhat dot com
- Cc: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Thu, 3 Sep 2009 08:38:30 -0700
- Subject: Re: [RFA] Use data cache for stack accesses
- References: <7e6c8d660907081308r13bff580rdcf4822c77df8403@mail.gmail.com> <200907082146.40513.pedro@codesourcery.com> <e394668d0908202300v2982d0c4y7e8f71d337f0b1d7@mail.gmail.com> <e394668d0908241748h769c8f8av1e3d8121688bc98f@mail.gmail.com> <m3hbvljcxp.fsf@fleche.redhat.com>
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.
[We can certainly pull the patch or default stack-cache to off if you like.]