From: "Theodore A. Roth" <troth@openavr.org>
To: gdb@sources.redhat.com
Subject: register_type method
Date: Sat, 14 Jun 2003 22:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0306141437490.16131-100000@bozoland.mynet> (raw)
Hi,
What builtin type should the *_register_type method return for the PC?
I would think that it it should be builtin_type_void_func_ptr like the d10v
does, but when I use that for the avr, I only get 2 bytes for the PC
register size and I need 4 bytes. Using builtin_type_uint32 works but just
doesn't feel right.
I also tried using builtin_type_CORE_ADDR and that seemed to work as well as
builtin_type_uint32.
Here's my avr_register_type method I'm currently playing with:
static struct type *
avr_register_type (struct gdbarch *gdbarch, int reg_nr)
{
if (reg_nr == AVR_PC_REGNUM)
/* return builtin_type_void_func_ptr; */
/* return builtin_type_uint32; */
return builtin_type_CORE_ADDR;
if (reg_nr == AVR_SP_REGNUM)
return builtin_type_void_data_ptr;
else
return builtin_type_uint8;
}
Ted Roth
next reply other threads:[~2003-06-14 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 22:29 Theodore A. Roth [this message]
2003-06-14 22:34 ` Daniel Jacobowitz
2003-06-15 0:02 ` Theodore A. Roth
2003-06-15 0:13 ` Daniel Jacobowitz
2003-06-15 0:16 ` Andrew Cagney
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=Pine.LNX.4.44.0306141437490.16131-100000@bozoland.mynet \
--to=troth@openavr.org \
--cc=gdb@sources.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