From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6756 invoked by alias); 1 Feb 2002 23:28:21 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6687 invoked from network); 1 Feb 2002 23:28:17 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 1 Feb 2002 23:28:17 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5EAF73E31; Fri, 1 Feb 2002 18:28:12 -0500 (EST) Message-ID: <3C5B248B.8070201@cygnus.com> Date: Fri, 01 Feb 2002 15:28:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Basic structure to describe register formats References: <20020201152209.A17528@nevyn.them.org> <3C5B0438.6010005@cygnus.com> <20020201162042.A20026@nevyn.them.org> <3C5B0D99.70601@cygnus.com> <20020201170917.A21225@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00017.txt.bz2 > You mean - 32:r1? >> >> I think the ``4'' indicates 4*2 hex digits. Digit pairs ordered either >> big or little endian. Yes it could be bits, however, the value would >> always need to be divisible by 8. > > > No, I don't think it needs to be divisible by 8. If it did I wouldn't > feel the need to represent the 8. > > For instance: > - ia64 has 1-bit registers that we currently transmit as either bytes > or words, IIRC. Here, I don't think we're worried about how many bits a register occupies. Rather, how that register is is represented when ``spilt'' into memory (to use the way the ia64 describes its in memory FP register format). It is that ``spilt'' format, transmitted as ascii encoded hex digit pairs, that is being described. A target with registers one bit in size could either spill each register into individual byte/word/... or combine them into a single word. For the latter, I think we'd end up with something like ``8:f0f1f2f3f4f5'', > - someone mentioned recently working on a non-8-bit target for GDB, > but he wasn't quite ready to contribute it. Yes. > But it will be divisible by 8 for now, so we'll just ignore that for > the moment. :-) Andrew