From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9371 invoked by alias); 17 May 2002 14:51:20 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9363 invoked from network); 17 May 2002 14:51:19 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 17 May 2002 14:51:19 -0000 Received: by fw-cam.cambridge.arm.com; id PAA00181; Fri, 17 May 2002 15:51:17 +0100 (BST) Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma029424; Fri, 17 May 02 15:50:38 +0100 Received: from cam-mail2.cambridge.arm.com (cam-mail2.cambridge.arm.com [172.16.1.91]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id PAA18783; Fri, 17 May 2002 15:50:37 +0100 (BST) Received: from sun18.cambridge.arm.com (sun18.cambridge.arm.com [172.16.2.18]) by cam-mail2.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id PAA07950; Fri, 17 May 2002 15:50:36 +0100 (BST) Message-Id: <200205171450.PAA07950@cam-mail2.cambridge.arm.com> To: Andrew Cagney cc: Richard.Earnshaw@arm.com, Elena Zannoni , gdb@sources.redhat.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Re: read_register_byte can't work with pseudo-reg model In-reply-to: Your message of "Fri, 17 May 2002 14:13:50 BST." <200205171313.OAA26418@cam-mail2.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 May 2002 07:51:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-05/txt/msg00221.txt.bz2 rearnsha@arm.com said: > Would the following tweak be acceptable? That is, only do the update > if the register has a name. > else if (REGISTER_NAME (regnum) != NULL && *REGISTER_NAME (regnum) > != '\0') > { > /* Is this register completely within the range the user is > writing? */ > if (myregstart <= regstart && regend <= myregend) > write_register_gen (regnum, myaddr + (regstart - myregstart)); > /* The register partially overlaps the range being written. */ > else > { I've just noticed that read_register_bytes is doing almost exactly this. Why do the two differ? R.