Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: jimb@redhat.com
Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Implementation of DW_OP_deref and DW_OP_deref_size operators
Date: Fri, 05 Jul 2002 19:10:00 -0000	[thread overview]
Message-ID: <200207052318.g65NIPR00673@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <npznx697nd.fsf@zwingli.cygnus.com> (message from Jim Blandy on 04 Jul 2002 22:27:02 -0500)

   Sender: jimb@zwingli.cygnus.com
   Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
   From: Jim Blandy <jimb@redhat.com>
   Date: 04 Jul 2002 22:27:02 -0500
   User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
   Content-Type: text/plain; charset=us-ascii


   Jim Blandy <jimb@redhat.com> writes:
   > Yes!  However, pointers are not always unsigned.  I think on some
   > 32-bit ABIs for 64-bit MIPS chips they need to be signed.  Andrew will
   > know the facts.

   But it doesn't matter whether pointers are unsigned.  The Dwarf spec
   says that DW_OP_deref pushes a value which is "the size of an address
   on the target machine", which is the full width of a Dwarf
   expression stack element; it doesn't need to be extended.  And it
   further says that DW_OP_deref_size zero-extends its argument.  So the
   patch looks correct to me.

Yup, I came to the same conclusion.  The code that was origionally
there also used unsigned pointers.

I'll check it in.

Thanks,

Mark


      reply	other threads:[~2002-07-05 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 16:00 Mark Kettenis
2002-07-04 18:34 ` Michal Ludvig
2002-07-04 20:23 ` Jim Blandy
2002-07-04 20:34   ` Jim Blandy
2002-07-05 19:10     ` Mark Kettenis [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=200207052318.g65NIPR00673@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@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