Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Delete another call to dwarf2read.c:decode_locdesc
Date: Wed, 19 Nov 2003 15:09:00 -0000	[thread overview]
Message-ID: <20031119150915.GB14955@nevyn.them.org> (raw)
In-Reply-To: <vt2ekw4g7mq.fsf@zenia.home>

On Wed, Nov 19, 2003 at 02:06:05AM -0500, Jim Blandy wrote:
> 
> Daniel Jacobowitz <drow@mvista.com> writes:
> > The global variables set according to the DW_OP_frame_base are no longer
> > used anywhere except decode_locdesc, and decode_locdesc is never called when
> > we should expect a frame-relative object; see the updated comments in the
> > patch below.  This function is now only used for member offsets, etc.;
> > partial symbols (DW_TAG_variable only); and common blocks, which act as
> > global variables.  The partial symbol case should either be eliminated or
> > changed to use computed locations.  The common block case probably likewise.
> > And the remaining cases expect constants.
> > 
> > So DW_OP_breg* and DW_OP_fbreg are dead wood at this point and can be
> > removed from this function.  They're handled entirely in the LOC_COMPUTED
> > support code.
> > 
> > These happened to be next on my campaign to whack global state from the
> > dwarf2 reader; marching slowly down the file.  Tested on i386-linux/dwarf2.
> > OK?
> 
> Superb!  Please commit.

Thanks, checked in.  Next are, I think, the sections pointers and the
members of comp_unit_head which belong in dwarf2_cu.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-11-19 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  1:26 Daniel Jacobowitz
2003-11-19  7:08 ` Jim Blandy
2003-11-19 15:09   ` Daniel Jacobowitz [this message]

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=20031119150915.GB14955@nevyn.them.org \
    --to=drow@mvista.com \
    --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