From: Daniel Jacobowitz <drow@false.org>
To: ligang@sunnorth.com.cn
Cc: gdb@sourceware.org
Subject: Re: register type as signed or unsigned?
Date: Tue, 10 Oct 2006 12:50:00 -0000 [thread overview]
Message-ID: <20061010125001.GA17340@nevyn.them.org> (raw)
In-Reply-To: <OF038E4AEA.A0A9C5E8-ON48257203.002DDCAC-48257203.002F6D81@sunnorth.com.cn>
On Tue, Oct 10, 2006 at 04:39:18PM +0800, ligang@sunnorth.com.cn wrote:
> hello all,
>
> I am porting GDB to a new target.
> I am not aware of the meaning of register type.
> You can do as follows:
> set_gdbarch_register_type (gdbarch, builtin_type_int32);
> or
> set_gdbarch_register_type (gdbarch, builtin_type_uint32);
>
> What is the real difference between the two situation?
> Why should GDB specify the register type as signed or unsigned?
> Dose it mean the former must use regcache_cooked_read_signed() and the
> latter must use
> regcache_cooked_read_unsigned()?
No; in fact, it doesn't make much difference. You should use whichever
is "more natural" for your target instruction set; it will affect
"print $reg" and "info reg".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-10 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 8:37 ligang
2006-10-10 12:50 ` Daniel Jacobowitz [this message]
2006-10-11 0:35 ` ligang
2006-10-11 0:48 ` Jan Kratochvil
2006-10-11 1:11 ` Paul Koning
2006-10-11 2:06 ` Daniel Jacobowitz
2006-10-11 7:00 ` 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=20061010125001.GA17340@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ligang@sunnorth.com.cn \
/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