From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19119 invoked by alias); 21 Jul 2011 11:13:59 -0000 Received: (qmail 19110 invoked by uid 22791); 21 Jul 2011 11:13:58 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Jul 2011 11:13:44 +0000 Received: (qmail 16372 invoked from network); 21 Jul 2011 11:13:44 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 21 Jul 2011 11:13:44 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [RFA 6/8] New port: TI C6x: gdbserver Date: Thu, 21 Jul 2011 12:21:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-8-generic; KDE/4.6.2; x86_64; ; ) Cc: Yao Qi References: <4E2638CE.7050205@codesourcery.com> <201107201855.09188.pedro@codesourcery.com> <4E27D5C7.5090707@codesourcery.com> In-Reply-To: <4E27D5C7.5090707@codesourcery.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201107211213.41018.pedro@codesourcery.com> 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: 2011-07/txt/msg00578.txt.bz2 On Thursday 21 July 2011 08:31:19, Yao Qi wrote: > >> + > >> + > >> + > >> + > >> + > > > > ... > > > > These are all general purpose, core registers, right? > > > > Not really. A0-31 and B0-31 are general purpose registers, even there > are some difference among different C6x cores (such as C62x, C67x, and > C64x). The rest of them can be regarded as control registers and status > registers. The target description should be refined for the different > C6x cores, and I'd like to do it in follow-up patches later. Is it OK? I'd rather start with things clean than change the target's register set after the fact, but I won't insist. At least you should document in the manual which registers the new standard feature org.gnu.gdb.tic6x.cpu requires (under Standard Target Features) though. -- Pedro Alves