From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4495 invoked by alias); 2 May 2003 22:26:16 -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 4488 invoked from network); 2 May 2003 22:26:15 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 2 May 2003 22:26:15 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 70FE92B2F; Fri, 2 May 2003 18:26:12 -0400 (EDT) Message-ID: <3EB2F084.6010203@redhat.com> Date: Fri, 02 May 2003 22:26:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Buettner Cc: gdb@sources.redhat.com Subject: Re: register_offset_hack() vs REGISTER_BYTE() References: <1030502003824.ZM26690@localhost.localdomain> <3EB1C2C8.5080502@redhat.com> <1030502010944.ZM27038@localhost.localdomain> <3EB1CA26.5080508@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00022.txt.bz2 > Can probably change REGISTER_BYTE to a pre-initialized method with predicate (see DEPRECATED_PC_IN_CALL_DUMMY for an example), and then add a predicate test for it to the above mix. On second thoughts, and having investigate things a bit further ... Doing it would revert any architecture [still] defining REGISTER_BYTE (almost all of them) back to using the legacy register cache. Consequently I'll instead just add sanity checks to ensure that the regcache and REGISTER_BYTE are consistent. > Sentinel frame should probably also be switched to using register_offset_hack(), instead of REGISTER_BYTE(), so that it is more consistent with the frame code. Appears to work. > Sounds like it's time to s/ REGISTER_BYTE / DEPRECATED_REGISTER_BYTE /. It isn't yet possible to eliminate that macro from the MIPS since it is that hardwired mystery that defines the MIPS remote protocol :-( ... Andrew