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]: LOC_COMPUTED + abstracted dwarf2 evaluator, again
Date: Thu, 30 Jan 2003 23:59:00 -0000	[thread overview]
Message-ID: <20030130235942.GA9973@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207081254320.23006-100000@dberlin.org>

On Mon, Jul 08, 2002 at 01:02:59PM -0400, Daniel Berlin wrote:
> For yer convenience,  I rediffed it against the current gdb sources.
> I'll update the changelog dates if it ever gets reviewed or approved.
> Slightly updated accompanying text (from the april submission):
> "
> The only real things left to do is give some *real* description in 
> locexpr_describe_location, add tracepoint support, and remove the 
> dwarf2cfi.c evaluator .  
> None of these should be blockers to committing it or reviewing it.
> 
> It would also be nice to use location expressions in *all* cases 
> (currently, it only does it for variables) so you can get rid of 
> decode_loc_desc, but i'll leave that for the next patch.
>  
> There are a few lines that are too long (<10, i *think*), sorry about 
> that, i couldn't see an easy way to break them up and have them make 
> sense.
> 
> Splitting this patch into loc_computed addition, and dwarf2 implementation 
> of loc_computed, doesn't make it much smaller (loc_computed_addition is 
> maybe 5% of the patch), so if size is a concern, sorry, but it's pretty 
> much unsplittable beyond that (the biggest portion is the addition of the 
> abstracted evaluator, but the dwarf2 implementation doesn't work without 
> it).
> 
> This patch has been tested on both powerpc-linux and 686-linux.
> "

FYI,

I've picked up this patch (well, an updated version Daniel sent me) and
I intend to get it working and resubmitted.  I've got it mostly passing
the testsuite now (there were a couple of problems, with frames and
such).  The tracepoint test will fail until that bit is implemented,
which I don't see as a blocker; I'll try to do that bit as a separate
patch afterwards.

I'm still working on cleaning up some bogosities, etc. etc., so it will
be another day or two.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      parent reply	other threads:[~2003-01-30 23:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 11:02 Daniel Berlin
2002-07-08 14:30 ` Jim Blandy
2002-07-08 16:44   ` Daniel Berlin
2002-07-08 19:03     ` Jim Blandy
2002-07-09 14:03 ` Jim Blandy
2002-07-09 14:08   ` Daniel Berlin
2002-07-09 15:47     ` Jim Blandy
2002-07-09 16:00       ` Daniel Berlin
2003-01-30 23:59 ` 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=20030130235942.GA9973@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