From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb-patches@sources.redhat.com>
Subject: Re: PATCH: Fix DW_OP_deref for DW_TAG_formal_parameter
Date: Thu, 31 Jul 2003 16:39:00 -0000 [thread overview]
Message-ID: <20030731163950.GA12667@lucon.org> (raw)
In-Reply-To: <20030731162207.GA24040@nevyn.them.org>
On Thu, Jul 31, 2003 at 12:22:07PM -0400, Daniel Jacobowitz wrote:
> On Thu, Jul 31, 2003 at 09:12:59AM -0700, H. J. Lu wrote:
> > On Thu, Jul 31, 2003 at 11:48:21AM -0400, Daniel Jacobowitz wrote:
> > > On Thu, Jul 31, 2003 at 08:44:05AM -0700, H. J. Lu wrote:
> > > > On Wed, Jul 30, 2003 at 08:27:53PM -0400, Daniel Jacobowitz wrote:
> > > > > On Wed, Jul 30, 2003 at 05:23:06PM -0700, H. J. Lu wrote:
> > > > > > On Wed, Jul 30, 2003 at 05:56:12PM -0400, Daniel Jacobowitz wrote:
> > > > > > > On Wed, Jul 30, 2003 at 02:54:21PM -0700, H. J. Lu wrote:
> > > > > > > > Does DW_OP_deref work correctly with gdb?
> > > > > > >
> > > > > > > That depends on the context. Things that use decode_locdesc, probably
> > > > > > > not. As we find time, things are being converted to the full
> > > > > > > expression evaluator. Location descriptions and frame bases should
> > > > > > > work.
> > > > > >
> > > > > > I don't think it does. Intel Fortran compiler generartes DW_OP_deref.
> > > > > > I got
> > > > >
> > > > > Location descriptions for parameters may not work fully. Feel free to
> > > > > fix it, or to investigate the reasons why more thoroughly - search for
> > > > > LOC_COMPUTED_ARG, but I don't even think we generate those yet.
> > > > >
> > > >
> >
> > > Please look more closely at what I suggested, and at how DW_OP_deref
> > > works for DW_TAG_variable (as opposed to DW_TAG_formal_parameter). All
> > > of the above should be turned into LOC_COMPUTED_ARG.
> > >
> >
> > Thanks. This patch works for me.
>
> Could you test this alternative? The goal is to eliminate calls to
> decode_locdesc.
>
Yes, it works.
Thanks.
H.J.
next prev parent reply other threads:[~2003-07-31 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030730215421.GA26408@lucon.org>
[not found] ` <20030730215612.GB15640@nevyn.them.org>
[not found] ` <20030731002306.GA28960@lucon.org>
[not found] ` <20030731002753.GA18866@nevyn.them.org>
[not found] ` <20030731154405.GA11592@lucon.org>
[not found] ` <20030731154821.GA10106@nevyn.them.org>
2003-07-31 16:13 ` H. J. Lu
2003-07-31 16:22 ` Daniel Jacobowitz
2003-07-31 16:39 ` H. J. Lu [this message]
2003-07-31 16:51 ` Daniel Jacobowitz
2003-07-31 20:12 ` Jim Blandy
2003-07-31 21:08 ` Daniel Jacobowitz
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=20030731163950.GA12667@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@sources.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