Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Andrew Stubbs <ams@codesourcery.com>,
	toolchain-devel@blackfin.uclinux.org,
	Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [PATCH v2] gdbserver: bfin: new port
Date: Mon, 13 Dec 2010 19:24:00 -0000	[thread overview]
Message-ID: <201012131423.26544.vapier@gentoo.org> (raw)
In-Reply-To: <201012131843.59666.pedro@codesourcery.com>

[-- Attachment #1: Type: Text/Plain, Size: 1395 bytes --]

On Monday, December 13, 2010 13:43:59 Pedro Alves wrote:
> > +++ b/gdb/regformats/reg-bfin.dat
> > +32:text_addr
> > +32:text_end_addr
> > +32:data_addr
> > +32:fdpic_exec
> > +32:fdpic_interp
> > +32:ipend
> 
> Hmmm.  These last 6 look to be some kind of pseudo registers, not
> part of the ISA -- I'm quite surprised to see these here, as
> part of the bfin core register set.  I understand these to be
> fdpic related; ISTR some discussion about making these be reported
> with a new qXfer object?  That'd be better, IMO.
> 
> I haven't looked at any bfin docs, but if any of the other
> registers aren't core registers (only available in some variants), you
> should consider implementing xml target register descriptions.

correct, these last 6 are the only pseudo regs from the ISA perspective.  the 
rest are actual hardware registers (well, the PC/CC registers are a little 
special, but i dont think that's relevant to this discussion).

i vaguely recall people voicing displeasure at the FDPIC implementation 
details in the past, but i'm not sure this is something that we can "recover" 
from.  Linux declares these things are registers via the ptrace ABI and 
gdbserver is merely forwarding that along.

also, the Blackfin port isnt doing anything new here.  we copied the decisions 
made by the FRV peeps and accepted into the gdb tree already.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-12-13 19:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  9:29 [PATCH v2] gdb: " 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 [this message]
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
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=201012131423.26544.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=ams@codesourcery.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=toolchain-devel@blackfin.uclinux.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