From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20370-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 25597 invoked by alias); 16 Dec 2004 16:44:23 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 25537 invoked from network); 16 Dec 2004 16:44:16 -0000
Received: from unknown (HELO go4.ext.ti.com) (192.91.75.132)
  by sourceware.org with SMTP; 16 Dec 2004 16:44:16 -0000
Received: from dlep90.itg.ti.com ([157.170.152.54])
	by go4.ext.ti.com (8.13.1/8.13.1) with ESMTP id iBGGiFj1019302
	for <gdb@sources.redhat.com>; Thu, 16 Dec 2004 10:44:15 -0600 (CST)
Received: from dlee2k70.ent.ti.com (localhost [127.0.0.1])
	by dlep90.itg.ti.com (8.12.11/8.12.11) with ESMTP id iBGGiALh021563
	for <gdb@sources.redhat.com>; Thu, 16 Dec 2004 10:44:15 -0600 (CST)
Received: from dlee2k02.ent.ti.com ([157.170.152.61]) by dlee2k70.ent.ti.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 16 Dec 2004 10:44:13 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Registry Group
Date: Thu, 16 Dec 2004 16:44:00 -0000
Message-ID: <C99FD21253EDE241A6E7FF989CFB493EEA3CE2@dlee2k02.ent.ti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Alexiev, Dobrin" <dalexiev@ti.com>
To: <gdb@sources.redhat.com>
X-OriginalArrivalTime: 16 Dec 2004 16:44:13.0090 (UTC) FILETIME=[792A6820:01C4E38E]
X-SW-Source: 2004-12/txt/msg00095.txt.bz2

I am working with the Eclipse C Development Tools community to add a
feature that will group registers in the Register View of Eclipse.=20

Since embedded CPUs have lots of peripheral registers (50-100+) it is
getting a burden for the developer to keep scrolling the registry view
to find the right register. A grouping will make the user experience way
better.=20

Since the IDE is relying on the GDB for most of the device information I
was wandering if there is a similar MI/GDB command to obtain the name of
the groups and their registers association.=20

In our product we added such command "-data-list-register-groups". The
syntax of the command is:=20
-data-list-register-groups
^done,register-groups=3D[{name=3D"r0",group=3D"GRP1"},{name=3D"r8",group=3D=
"GRP2"}
]
It is created similar to "-data-list-register-names".

I found opened enhancement request for this - "850 - Missing MI
interface to register groups". In case that is not implemented we can
offer to submit patch for GDB that will support this command.=20

Any other ideas will be appreciated.=20
Thanks

Dobrin Alexiev
Texas Instruments=20