From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>,
toolchain-devel@blackfin.uclinux.org,
Jie Zhang <jie.zhang@analog.com>
Subject: Re: [PATCH v3] gdb: bfin: new port
Date: Tue, 14 Dec 2010 21:31:00 -0000 [thread overview]
Message-ID: <201012142131.22802.pedro@codesourcery.com> (raw)
In-Reply-To: <1292359346-22447-1-git-send-email-vapier@gentoo.org>
On Tuesday 14 December 2010 20:42:26, Mike Frysinger wrote:
> + /* Pseudo Registers */
> + BFIN_PC_REGNUM,
> + BFIN_CC_REGNUM,
> + BFIN_TEXT_ADDR, /* Address of .text section. */
> + BFIN_TEXT_END_ADDR, /* Address of the end of .text section. */
> + BFIN_DATA_ADDR, /* Address of .data section. */
> +
> + BFIN_FDPIC_EXEC_REGNUM,
> + BFIN_FDPIC_INTERP_REGNUM,
> +
I thought these (text_addr ... fdpic*) would be removed?
Can you explain why are the PC and CC registers pseudo
registers, but supported as being raw registers anyway? Couldn't
gdb compute them itself from the other registers, with
gdb's pseudo register support (gdbarch_pseudo_register_read|write)?
googling I found you mentioning that the "CC pseudo register can
be deduced from the ASTAT register", though further googling doesn't
find any mention of what ASTAT is. I'm sure there's a good reason,
I'm probably just missing a comment somewhere.
--
Pedro Alves
next prev parent reply other threads:[~2010-12-14 21:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:29 [PATCH v2] " Mike Frysinger
2010-12-09 9:31 ` [PATCH v2] gdbserver: " Mike Frysinger
2010-12-13 18:44 ` Pedro Alves
2010-12-13 19:24 ` Mike Frysinger
2010-12-14 9:37 ` Andrew Stubbs
2010-12-14 15:10 ` Mike Frysinger
2010-12-14 16:31 ` Pedro Alves
2010-12-14 16:58 ` Mike Frysinger
2010-12-14 17:16 ` Andrew Stubbs
2010-12-14 17:26 ` Mike Frysinger
2010-12-15 11:54 ` Andrew Stubbs
2010-12-15 12:55 ` [toolchain-devel] " Mike Frysinger
2010-12-15 13:17 ` Andrew Stubbs
2010-12-14 17:40 ` Pedro Alves
2010-12-14 17:48 ` Mike Frysinger
2010-12-14 18:06 ` Pedro Alves
2010-12-14 18:21 ` Mike Frysinger
2010-12-15 16:54 ` Mike Frysinger
2010-12-14 6:03 ` [PATCH v2] gdb: " Joel Brobecker
2010-12-14 16:14 ` Mike Frysinger
2010-12-14 20:43 ` [PATCH v3] " Mike Frysinger
2010-12-14 21:31 ` Pedro Alves [this message]
2010-12-14 22:01 ` Mike Frysinger
2010-12-15 13:02 ` Mike Frysinger
2010-12-15 16:53 ` Pedro Alves
2010-12-15 17:08 ` Mike Frysinger
2010-12-15 18:01 ` Pedro Alves
2010-12-15 18:38 ` Mike Frysinger
2010-12-15 18:42 ` Pedro Alves
2010-12-15 18:16 ` Mike Frysinger
2010-12-15 18:25 ` Pedro Alves
2010-12-14 21:48 ` [PATCH v3] gdbserver: " Mike Frysinger
2010-12-14 23:03 ` Ralf Corsepius
2010-12-15 0:15 ` Mike Frysinger
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=201012142131.22802.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jie.zhang@analog.com \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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