From: "Anmol P. Paralkar" <b07584@freescale.com>
To: gdb@sourceware.org
Subject: Question on power-core.xml, register: r1.
Date: Fri, 09 May 2008 23:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0805091823590.22847@ld0159-tx32> (raw)
Hello,
Per Appendix F, Sec. F.3 Predefined Target Types, of the GDB User Manual:
code_ptr
data_ptr
Pointers to unspecified code and data. The program counter and any
dedicated return address register may be marked as code pointers; printing
a code pointer converts it into a symbolic address. The stack pointer and
any dedicated address registers may be marked as data pointers.
I note the use of the term: "may"; while power-core.xml marks 'pc' and 'lr'
as type="code_ptr", it does not mark 'r1', the stack-pointer as
type="data_ptr". Is there a specific reason why this is so? It's type="uint32";
marking 'pc' & 'lr' as type="code_ptr" has the advantage of converting their
values into symbollic address, what would happen (and is not) were 'r1' to be
marked type="data_ptr"?
Thanks,
Anmol.
next reply other threads:[~2008-05-09 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 23:41 Anmol P. Paralkar [this message]
2008-05-11 21:30 ` Daniel Jacobowitz
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.64.0805091823590.22847@ld0159-tx32 \
--to=b07584@freescale.com \
--cc=gdb@sourceware.org \
/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