From: Daniel Jacobowitz <drow@false.org>
To: Paul Brook <paul@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: RFC: Available registers as a target property
Date: Mon, 09 May 2005 16:32:00 -0000 [thread overview]
Message-ID: <20050509163220.GC20242@nevyn.them.org> (raw)
In-Reply-To: <200505091657.46412.paul@codesourcery.com>
On Mon, May 09, 2005 at 04:57:46PM +0100, Paul Brook wrote:
> On Friday 06 May 2005 17:20, Daniel Jacobowitz wrote:
> > set:<NAME>:<PROTOCOL NUMBER>
> >...
> > reg:<NAME>:<PROTOCOL NUMBER>:<BITSIZE>:<TYPE>:<TARGET DATA>...
>
> Would it make sense to allow these two overlap? ie. if gdb can understand the
> set it will use that and ignore the associated reg entries. If it doesn't
> understand the set it will use the individual set entries.
>
> Assume I have an coprocessor not currently supported by gdb (Arm maverick for
> the sake of argument), and a target that exposes maverick registers via reg:.
>
> At some time in the future gdb implements proper maverick support, and adds
> set:maverick. Under your proposal I can't use my old gdb with my new target.
> My new target doesn't generate reg: entries for maverick regs, and my old gdb
> doesn't understand set:maverick.
>
> Obviously this is is purely a backwards compatibility QoI issue, and doesn't
> matter if you expect everyone to use latest gdb.
>
> I'd suggest:
> reg:<NAME>:<SET NAME>:<PROTOCOL NUMBER>:<BITSIZE>:<TYPE>:<TARGET DATA>...
>
> Where <SET NAME> can be empty if the register doesn't belong to a known set.
> In fact I guess including the set name in the reg: component makes the set:
> component redundant.
I've envisioned a different solution to this problem. The set
information does not need to come from the target; GDB can recognize it
via pattern information. "If we have eight registers named this of
these types, and eight registers named that of those types, then that's
this coprocessor".
I do see that there's some fudge factor here because register names and
types aren't a very good key. How about the tags field that I
mentioned in my last mail to Mark, which is basically the same as set?
If you report a set, you are relying upon GDB to recognize it or choose
to ignore the associated registers.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-09 16:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 16:20 Daniel Jacobowitz
2005-05-07 10:25 ` Eli Zaretskii
2005-05-07 16:19 ` Daniel Jacobowitz
2005-05-07 19:37 ` Eli Zaretskii
2005-05-09 15:37 ` Daniel Jacobowitz
2005-05-09 20:58 ` Eli Zaretskii
2005-05-07 16:04 ` Mark Kettenis
2005-05-09 16:20 ` Daniel Jacobowitz
2005-05-09 15:57 ` Paul Brook
2005-05-09 16:32 ` Daniel Jacobowitz [this message]
2005-05-09 21:33 ` Chris Zankel
2005-05-09 23:07 ` Daniel Jacobowitz
2005-05-10 0:23 ` Chris Zankel
2005-05-10 21:08 ` Daniel Jacobowitz
2005-05-12 23:35 ` Chris Zankel
2005-05-17 14:03 ` Daniel Jacobowitz
2005-05-10 0:54 ` Ramana Radhakrishnan
2005-05-10 21:14 ` Daniel Jacobowitz
2005-05-17 19:32 ` Daniel Jacobowitz
2005-05-18 9:29 ` Richard Earnshaw
2005-05-19 1:00 ` Daniel Jacobowitz
2005-05-20 14:54 ` Richard Earnshaw
2005-05-09 22:39 Paul Schlie
2005-05-10 0:03 Paul Schlie
2005-05-10 11:12 Paul Schlie
2005-05-17 23:08 Paul Schlie
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=20050509163220.GC20242@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=paul@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).