From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22615-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 13397 invoked by alias); 23 Sep 2005 17:12: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 13361 invoked by uid 22791); 23 Sep 2005 17:12:12 -0000
Received: from host217-40-213-68.in-addr.btopenworld.com (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 23 Sep 2005 17:12:12 +0000
Received: from mace ([192.168.1.25]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 23 Sep 2005 18:12:10 +0100
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Vladimir Prus'" <ghost@cs.msu.su>,
	<gdb@sources.redhat.com>
Subject: RE: Targets with non-byte-addressable memory
Date: Fri, 23 Sep 2005 17:12:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To:  <dh0fuj$2nu$1@sea.gmane.org>
Message-ID: <SERRANORNZSPGNkY5Te00000236@SERRANO.CAM.ARTIMI.COM>
X-SW-Source: 2005-09/txt/msg00170.txt.bz2

----Original Message----
>From: Vladimir Prus
>Sent: 23 September 2005 09:56

> Hello!
> 
> Does anybody has experience of porting gdb to a target where memory is not
> byte-addressable. That is, if you read 0x80000007 you get 4 bytes and if
> you read 0x80000008 you get another 4 bytes.
> 
> The source has TARGET_CHAR_BIT macro, but no target under "config" makes
> use of them which makes me suspect that setting it won't do any good. In
> fact, after setting it to 32, I get compile error in ax-gdb.c:
> 
>         case 8 / TARGET_CHAR_BIT:
>           ax_simple (ax, aop_ref8);
>           break;
>         case 16 / TARGET_CHAR_BIT:
>           ax_simple (ax, aop_ref16);
>           break;
>         case 32 / TARGET_CHAR_BIT:
>           ax_simple (ax, aop_ref32);
>           break;
>         case 64 / TARGET_CHAR_BIT:
>           ax_simple (ax, aop_ref64);
> 
> as both 8/32 and 16/32 give 0, and I get duplicate case label.


  Changing TARGET_CHAR_BIT is the wrong way to go.  Basically, IIUIC, you
shouldn't need to do anything at all for native debugging, and for remote
debugging, you'll have to take care of it in the stub/server.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....