Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: dwarf2expr.[ch]
Date: Tue, 09 Jul 2002 16:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0207091853240.22894-100000@dberlin.org> (raw)
In-Reply-To: <npznx036c6.fsf@zwingli.cygnus.com>

On 9 Jul 2002, Jim Blandy wrote:

> 
> Daniel Berlin <dberlin@dberlin.org> writes:
> > I also can't remember why get_subr was needed, and never implemented it.
> > Refresh my memory if you could, since you wrote the spec?
> > :)
> 
> It's for DW_OP_call*, which the evaluator here doesn't implement.
> 
> > I've only reposted it for completeness sake, i'll include it again when i 
> > revise the loc_computed patch.
> 
> Actually, let's keep this evaluator discussion separate --- we can get
> this reviewed and committed without dealing with anything else.

Well, okay, but fair warning:
either patch will take me at least a few weeks before i resubmit.
While I had time back in April, law clerking is keeping me very busy, and 
i'm wrapped up in gcc stuff on the side.
So if you have a deadline or something, ....
I dunno, i just get the feeling from the sentence that you want to get 
this out of the way sooner than that, so i figured it's only fair i make 
sure you don't have the notion that i'll get to it RSN.

It might make sense to cheat and do
value_as_long (value_binop (value_from_long (v1), value_from_long (v2), BINOP_RSH))
etc
for binops/things that need masking.or something, so we can keep the 
result as a LONGEST, but not worry about  
masking during the operations


  reply	other threads:[~2002-07-09 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 16:48 Daniel Berlin
2002-07-08 20:20 ` Andrew Cagney
2002-07-08 20:49   ` Daniel Berlin
2002-07-08 21:12 ` Andrew Cagney
2002-07-09 15:21   ` Jim Blandy
2002-07-10  9:05     ` Andrew Cagney
2002-07-09 15:10 ` Jim Blandy
2002-07-09 16:00   ` Daniel Berlin [this message]
2002-07-10 11:18   ` Daniel Berlin
2002-07-10 12:48     ` Jim Blandy
2002-07-10 13:27       ` Daniel Berlin
2002-07-10 16:15         ` Jim Blandy

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=Pine.LNX.4.44.0207091853240.22894-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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