From: Jim Blandy <jimb@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
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: Thu, 04 Jul 2002 20:34:00 -0000 [thread overview]
Message-ID: <npznx697nd.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <npofdmanjb.fsf@zwingli.cygnus.com>
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.
next prev parent reply other threads:[~2002-07-05 3:27 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 [this message]
2002-07-05 19:10 ` Mark Kettenis
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=npznx697nd.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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