Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Handle DWARF-2 value pieces residing in *parts* of a register
Date: Mon, 04 Jan 2010 15:07:00 -0000	[thread overview]
Message-ID: <201001041507.o04F735j013316@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <m3r5qo9i9e.fsf@fleche.redhat.com> from "Tom Tromey" at Dec 21, 2009 01:36:29 PM

Tom Tromey wrote:
> >>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
> 
> Ulrich> Now, according to the DWARF-2 standard, the location of register pieces
> Ulrich> of smaller than full register size is defined by the platform ABI.
> Ulrich> For the placement of a small value in a *single* register we have a
> Ulrich> gdbarch callback (gdbarch_value_from_register); maybe we need something
> Ulrich> like that for value pieces as well.  At the very least, we ought to
> Ulrich> you the same default as default_value_from_register does: assume
> Ulrich> partial register use implies the least-significant part of the register.
> 
> Ulrich> The patch below implements this.
> 
> I think this seems reasonable.
> 
> It seems straightforward enough to add an arch method if we ever
> actually need one.  I wouldn't worry about it unless we already know of
> such a machine.

Thanks for the review.  I've checked the patch in now.

> Ulrich> 	a register, assume the least-signficant part is used.
> 
> Typo, "significant".

Fixed, thanks!

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2010-01-04 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 15:32 Ulrich Weigand
2009-12-21 20:36 ` Tom Tromey
2010-01-04 15:07   ` Ulrich Weigand [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=201001041507.o04F735j013316@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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