From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22548 invoked by alias); 13 Dec 2010 19:24:08 -0000 Received: (qmail 22537 invoked by uid 22791); 13 Dec 2010 19:24:07 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 13 Dec 2010 19:24:03 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 40B1E1B400B; Mon, 13 Dec 2010 19:24:01 +0000 (UTC) From: Mike Frysinger To: Pedro Alves Subject: Re: [PATCH v2] gdbserver: bfin: new port Date: Mon, 13 Dec 2010 19:24:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.37-rc5; KDE/4.5.2; x86_64; ; ) Cc: gdb-patches@sourceware.org, Andrew Stubbs , toolchain-devel@blackfin.uclinux.org, Daniel Jacobowitz References: <1291886957-12003-1-git-send-email-vapier@gentoo.org> <1291887065-12093-1-git-send-email-vapier@gentoo.org> <201012131843.59666.pedro@codesourcery.com> In-Reply-To: <201012131843.59666.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1404257.n6BPgxMbqE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201012131423.26544.vapier@gentoo.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-12/txt/msg00196.txt.bz2 --nextPart1404257.n6BPgxMbqE Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-length: 1388 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 >=20 > 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. >=20 > 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. t= he=20 rest are actual hardware registers (well, the PC/CC registers are a little= =20 special, but i dont think that's relevant to this discussion). i vaguely recall people voicing displeasure at the FDPIC implementation=20 details in the past, but i'm not sure this is something that we can "recove= r"=20 from. Linux declares these things are registers via the ptrace ABI and=20 gdbserver is merely forwarding that along. also, the Blackfin port isnt doing anything new here. we copied the decisi= ons=20 made by the FRV peeps and accepted into the gdb tree already. -mike --nextPart1404257.n6BPgxMbqE Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQIcBAABAgAGBQJNBnKuAAoJEEFjO5/oN/WBX7EP/27vgFJSZ9SYKN0V0qMNkwVB c4DaW8vMONkKuMBo2KpbFjyWLPoTItcxNVck3QGPGx9Nzrna4J4RV10bZFTduPdg KCUOqHMAJSSntMuiKfZD5j0z8dhQMdhPRGnu+17geTKRsI33uN3TjMJDImMItLRx Dslgf22cHaIXR7WNK7XahlS78RtW/3sG4sks6C+X1d7myDq0aXbZrlLhXAOSJkJR ZVekYUg235rHsGPNSXVcwzulH0qgSwUzRFNEMmn0LcmHYD9RPIZh9ot3oKexbkAk CqL06XE7dKBQcl6N4bgnX1LTpDpQkD616AI+C+AO3VgLlRLyoobT3Too11ga0ncB w5Z7wozz7cAE3wiyvc1K8xi/6dprYSuCgbpNu19XTMVF3eZ7vGvu0mGPivPH5vOH 01lWXX+VNt4kZ8HyA38AcN+YzTiMRIXp+JG+JqEvud38aWtuP/9VmH/15BJcMFsM lOFRIN+16C90poWV9dXv++lOwLT2ky6qTFiD5wGS51we92f2iwucgBZ5Bt3kiCYv gyX/8xjPMh6+VMEuaBYWcaAM2apSfRLDcvp1qPRu2QIqzjnY7GxIgOiK8OgQR0FN rjI4UPw6EaLB7y41mf2YwvNliIGZrCoh4F7nxI9ZQL+drzQJxesAZO+28PGQLnrF yN2THz+GhoQ4cMguKpXh =aMtu -----END PGP SIGNATURE----- --nextPart1404257.n6BPgxMbqE--