From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: "'Tom Tromey'" <tromey@redhat.com>, <gdb-patches@sourceware.org>,
"'FPC Core Developer List'" <core@freepascal.org>
Subject: RE: [RFA] dwarf debug format: Support DW_AT_variable_parameter attribute
Date: Mon, 17 May 2010 21:48:00 -0000 [thread overview]
Message-ID: <001201caf60a$43b76a00$cb263e00$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100517174726.GK2805@adacore.com>
Whoops,
you are right:
this was Tom's question:
>I wonder whether it is possible for such a parameter to be marked as
>LOC_COMPUTED or LOC_OPTIMIZED_OUT by var_decode_location. If so then
>changing the class to LOC_REF_ARG seems incorrect.
I looked a little more into the sources
and now understand that my patch is indeed
wrong :(
I hoped that simple case like variables in registers
or at a fixed offset relative to stack would simply
be treated as in stabs and assign a LOC_REGISTER
or LOC_ARG SYMBOL_CLASS,
but there is no such conversion ...
See note line 8459 from dwarf2read.c source.
/* NOTE drow/2002-01-30: It might be worthwhile to have a static
expression evaluator, and use LOC_COMPUTED only when necessary
(i.e. when the value of a register or memory location is
referenced, or a thread-local block, etc.). Then again, it might
not be worthwhile. I'm assuming that it isn't unless performance
or memory numbers show me otherwise. */
I fear that my patch will have to wait until
this static expression evaluator is implemented...
Let's drop this patch for now.
Thanks for the clever question, Tom!
Pierre
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Monday, May 17, 2010 7:47 PM
> À : Pierre Muller
> Cc : 'Tom Tromey'; gdb-patches@sourceware.org
> Objet : Re: [RFA] dwarf debug format: Support DW_AT_variable_parameter
> attribute
>
> > So, may I commit this patch?
>
> As far as I can tell, there was a question from Tom that is still
> unanswered...
>
> --
> Joel
next prev parent reply other threads:[~2010-05-17 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8830.7035308846$1273670829@news.gmane.org>
2010-05-13 17:51 ` Tom Tromey
2010-05-17 17:34 ` Joel Brobecker
2010-05-17 17:34 ` Pierre Muller
2010-05-17 18:54 ` Joel Brobecker
2010-05-17 21:48 ` Pierre Muller [this message]
[not found] ` <44296.7587885962$1274132782@news.gmane.org>
2010-05-19 19:43 ` Tom Tromey
2010-05-19 21:45 ` Pierre Muller
[not found] ` <28559.2589797036$1274302480@news.gmane.org>
2010-05-19 22:34 ` Tom Tromey
2010-05-19 23:34 ` [RFA-v2] " Pierre Muller
[not found] ` <27418.1569614031$1274308493@news.gmane.org>
2010-05-21 17:44 ` Tom Tromey
2010-05-21 20:50 ` Pierre Muller
2010-11-04 5:32 ` [new testcase] Regression 7.1->7.2 for iFort [Re: [RFA-v2] dwarf debug format: Support DW_AT_variable_parameter attribute] Jan Kratochvil
2010-11-04 8:47 ` [Core] " Pierre Free Pascal
2010-11-04 18:01 ` Joel Brobecker
2010-11-05 8:04 ` Pierre Free Pascal
2011-09-01 7:20 ` Jan Kratochvil
2010-05-12 13:27 [RFA] dwarf debug format: Support DW_AT_variable_parameter attribute Pierre Muller
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='001201caf60a$43b76a00$cb263e00$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--cc=core@freepascal.org \
--cc=gdb-patches@sourceware.org \
--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