Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Use better types for ARM registers
Date: Fri, 23 Jun 2006 13:01:00 -0000	[thread overview]
Message-ID: <20060623130150.GA17559@nevyn.them.org> (raw)
In-Reply-To: <1150887507.25267.8.camel@pc960.cambridge.arm.com>

On Wed, Jun 21, 2006 at 11:58:27AM +0100, Richard Earnshaw wrote:
> I can't see any problems with this.  Abstractly, registers are just
> buckets of bits, it's the use context that determines whether they are
> signed or unsigned (or something else entirely).  In some ways it might
> be nice if we could enforce all interpretation of the bits to be
> explicit, but I can see that might be an unnecessary overhead.  I guess
> interpreting the value by default as unsigned is closer to my ideal than
> defaulting to signed.

Thanks, checked in.  I agree it'd be nice, but I don't think it's
practical.

> One of the things that has always frustrated me with GDB is to print out
> the value of an integer register (or pair of such registers) as a
> floating point value -- ie, there's no obvious way to do the equivalent
> of *(double*)&regnum.

Hmm, I'll keep this message around... really the implementation would
be easy, we'd just need a syntax.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-06-23 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 19:45 Daniel Jacobowitz
2006-06-21 10:59 ` Richard Earnshaw
2006-06-23 13:01   ` Daniel Jacobowitz [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=20060623130150.GA17559@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=rearnsha@arm.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