From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24206 invoked by alias); 10 May 2002 18:42:51 -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 24199 invoked from network); 10 May 2002 18:42:50 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 10 May 2002 18:42:50 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C0D253DEC; Fri, 10 May 2002 14:42:58 -0400 (EDT) Message-ID: <3CDC14B2.4030407@cygnus.com> Date: Fri, 10 May 2002 11:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc1) Gecko/20020429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: Re: ARM and virtual/raw registers References: <200205101629.RAA06801@cam-mail2.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00111.txt.bz2 > If, as I understand your previous postings to imply, having pseudo > registers stored in the cache is wrong, why does regcache_read() allow > them? > > regcache_read (int rawnum, char *buf) > { > gdb_assert (rawnum >= 0 && rawnum < (NUM_REGS + NUM_PSEUDO_REGS)); Lets just pretend you didn't see that :-) Some existing mechanisms store pseudo-register values in the cache. In addition ``NUM_REGS'' is overloaded - it controls too many aspects of GDB - num regs in G packet, num regs to save across an inferior function call, ... Andrew