From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5403 invoked by alias); 28 Jun 2004 14:03:27 -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 5391 invoked from network); 28 Jun 2004 14:03:26 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 28 Jun 2004 14:03:26 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5SE3Pe3003707 for ; Mon, 28 Jun 2004 10:03:25 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5SE3O005187; Mon, 28 Jun 2004 10:03:24 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2E1522B9D; Mon, 28 Jun 2004 10:03:20 -0400 (EDT) Message-ID: <40E02528.7060906@gnu.org> Date: Mon, 28 Jun 2004 14:51:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Randolph Chung , Michael Elizabeth Chastain Cc: gdb@sources.redhat.com Subject: Re: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit References: <20040627042052.CABC44B104@berman.michael-chastain.com> <20040627184026.GC795@tausq.org> In-Reply-To: <20040627184026.GC795@tausq.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00272.txt.bz2 >>ac> What's the ABI wordsize - the size of a register pushed onto the stack? >>> ac> "info registers" should be using that register size and looking at the >>> ac> HP/PA code, that appears to be the case. >>> >>> It's 4 bytes, all right. Lets expand the list (you can get much of this from sizeof.exp): - sizeof (saved register) - sizeof (int) - sizeof (long) - sizeof (void *) - sizeof (long long) - sizeof (ptrace/ktrace register) > The hppa target naming conventions are a bit weird (to me, at least) I'm guessing that we're missing one: hppa1.x executable. Since michael stated that registers were being saved as 4-bytes, I think we're looking at this one. > hppa2.0w-*-* is a 32-bit target, however the w means that you can use > 64-bit registers and the pa2.0 64-bit opcodes (ldd, std, etc) This is sounding a lot like MIPS N32: 8 - sizeof (saved register) 4 - sizeof (int) 4 - sizeof (long) 4 - sizeof (void *) 8 - sizeof (long long) 8 - sizeof (ptrace/ktrace register) > hppa64-*-* is the 64-bit target. > > >>> The funny thing is, gdb 6.1.1 "maint print registers" says that >>> r19 is 4 bytes long, but "info reg r19" has special code to print >>> all 8 bytes of it. >>> >>> I'm still kinda dubious, but if it's okay with randolph that the >>> debugger quietly operates in 32-bit mode, it's okay with me. >>> I would do something like this: > > > Yes, i think this is ok. This is getting into 32x64 - there be dragons. Andrew