From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14632 invoked by alias); 16 May 2002 12:19:39 -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 14601 invoked from network); 16 May 2002 12:19:37 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 16 May 2002 12:19:37 -0000 Received: by fw-cam.cambridge.arm.com; id NAA03228; Thu, 16 May 2002 13:19:34 +0100 (BST) Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma002740; Thu, 16 May 02 13:19:12 +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 NAA13989; Thu, 16 May 2002 13:19:11 +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 NAA16585; Thu, 16 May 2002 13:19:10 +0100 (BST) Message-Id: <200205161219.NAA16585@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 "Wed, 15 May 2002 15:43:33 EDT." <3CE2BA65.4090001@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 May 2002 05:19:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-05/txt/msg00185.txt.bz2 > I'm guessing. Try: > > if (REGISTER_READ_P ()) > { > do something fairly sane; > } > else > { > all the legacy cruft including the call to > legacy_read_register_gen() and that test. > } > > Thing is that there is only one target in the FSF using > READ_REGISTER_P() so there is this dividing line - something using > read_register_p() can be given far stronger requirements than for the > older code. Which target is that, and where is READ_REGISTER_P ? I can't find anything in the either the source or the mailing lists. Mind you, the web-based mailing list search even fails to find your message when I search for READ_REGISTER_P. R.