From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21237 invoked by alias); 12 May 2002 15:25:15 -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 21228 invoked from network); 12 May 2002 15:25:14 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 12 May 2002 15:25:14 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8F5723E07; Sun, 12 May 2002 11:25:23 -0400 (EDT) Message-ID: <3CDE8963.9020506@cygnus.com> Date: Sun, 12 May 2002 08:25: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: <200205121419.PAA29377@cam-mail2.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00124.txt.bz2 > Having either the debug-info register numbers See my other reply. The debug-info registers do not impose order on the register cache. > or a single target impose an > order on the regcache is broken. And fixing remote.c is on the hit list (I should fix Daniel's bug) :-) It already has an internal table that does a mapping only it is 1:1. remote.c is complicated, however. The mapping will need to be defined at run (and not compile) time - this makes trying to perform transformations (and not simple mappings) on the way through more difficult. > Consider the case where we have two > target interfaces that need to mandate different orderings; clearly one of > them must fail. Similarly, having the debug-info mandate an ordering is > equally broken -- consider two ABIs which use different numbering in the > debug info. Clearly, the only way to solve this is to have mapping > layers, at least in concept, at each interface. Then the tdep code is > free to select any ordering it likes in the cache; typically an ordering > that will lead to greatest efficiency. Here, you're preaching to the converted :-) enjoy, Andrew