Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fix big-endian bug with DWARF_VALUE_STACK
Date: Wed, 24 Feb 2010 16:30:00 -0000	[thread overview]
Message-ID: <m3zl2yvbo4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201002241411.o1OEBrHC011378@d12av02.megacenter.de.ibm.com> 	(Ulrich Weigand's message of "Wed, 24 Feb 2010 15:11:53 +0100 (CET)")

>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:

Ulrich> This seems somewhat different in that the DW_OP_implicit_value
Ulrich> explicitly provides data of a certain length.  On the other
Ulrich> hand, DW_OP_stack_value refers to the value on top of the stack,
Ulrich> which -as I understand it- is a numerical value, not a sequence
Ulrich> of bytes of defined length.

Elements on the operand stack are explicitly address-sized.  From DWARF
1.11.1:

    Each element of the stack is the size of an address on the target
    machine.

Ulrich> So it would seem to me that you should be able to request that
Ulrich> this value be represented in any arbitrary length ...

That interpretation makes sense to me, but so does the one making it an
error.  I suspect we will never run across code that exercises this.  If
you want to change it, I have no objection.

Tom


  parent reply	other threads:[~2010-02-24 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 16:08 Tom Tromey
2010-02-23 16:16 ` Tom Tromey
2010-02-23 19:53 ` Ulrich Weigand
2010-02-23 20:26   ` Tom Tromey
2010-02-24 14:12     ` Ulrich Weigand
2010-02-24 14:20       ` Mark Wielaard
2010-02-24 16:10         ` Ulrich Weigand
2010-02-24 16:30       ` Tom Tromey [this message]
2010-02-25 20:44         ` Ulrich Weigand
2010-02-25 21:03           ` Tom Tromey
2010-02-26 12:50             ` Ulrich Weigand

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=m3zl2yvbo4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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