From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6007 invoked by alias); 29 Apr 2003 15:20:41 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5988 invoked from network); 29 Apr 2003 15:20:40 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 29 Apr 2003 15:20:40 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3DA372B2F; Tue, 29 Apr 2003 11:20:39 -0400 (EDT) Message-ID: <3EAE9847.90809@redhat.com> Date: Wed, 30 Apr 2003 14:28: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: Daniel Jacobowitz Cc: Mark Kettenis , colins@google.com, gdb-patches@sources.redhat.com Subject: Re: re-ordered i386 regcache References: <20030428153247.GA28501@nevyn.them.org> <3EAD51F1.8050605@redhat.com> <20030428161443.GA30324@nevyn.them.org> <3EAD58B8.2070003@redhat.com> <20030428192506.GA11978@nevyn.them.org> <3EADB095.2090409@redhat.com> <20030428233106.GA7307@nevyn.them.org> <3EADE027.90209@redhat.com> <20030429044506.GA11200@nevyn.them.org> <3EAE8C6B.2050403@redhat.com> <20030429150810.GA12043@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00543.txt.bz2 > All three require a projection such that, assumed contigious, debug info >> registers project onto raw registers. Isn't this what i386 has? > > > I don't think so. All three need a view of registers slightly > different from the "normal" one, but they don't have "assumed > contiguous debug info registers". In fact in e500 they're assumed > not-contiguous. Please study the code. A 32 bit MIPS ABI on a 64 bit MIPS represents long long as two 32 bit sub-parts of two 64 bit registers; the two 32 bit parts are assumed to be adjacent. The adjacent assumption will eventually be lifted, but that will be done by someone implementing something like location descriptions. Andrew