From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16609 invoked by alias); 26 Nov 2005 17:52:32 -0000 Received: (qmail 16600 invoked by uid 22791); 26 Nov 2005 17:52:31 -0000 X-Spam-Check-By: sourceware.org Received: from hiauly1.hia.nrc.ca (HELO hiauly1.hia.nrc.ca) (132.246.100.193) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 26 Nov 2005 17:52:29 +0000 Received: from hiauly1.hia.nrc.ca (hiauly1.hia.nrc.ca [127.0.0.1] (may be forged)) by hiauly1.hia.nrc.ca (8.12.9-20030917/8.12.9) with ESMTP id jAQHqQqO004038; Sat, 26 Nov 2005 12:52:26 -0500 (EST) Received: (from dave@localhost) by hiauly1.hia.nrc.ca (8.12.9-20030917/8.12.9/Submit) id jAQHqPrA004033; Sat, 26 Nov 2005 12:52:25 -0500 (EST) Message-Id: <200511261752.jAQHqPrA004033@hiauly1.hia.nrc.ca> Subject: Re: Register numbers on hppa64 To: mark.kettenis@xs4all.nl (Mark Kettenis) Date: Sat, 26 Nov 2005 18:00:00 -0000 From: "John David Anglin" Cc: randolph@tausq.org, gdb@sources.redhat.com, brobecker@adacore.com In-Reply-To: <200511261734.jAQHY5nH000878@elgar.sibelius.xs4all.nl> from "Mark Kettenis" at Nov 26, 2005 06:34:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00584.txt.bz2 > But we have a de-facto ABI since GCC has been using > DBX_REGISTER_NUMBER for all non-CFI DWARF2 output. I never noticed > DWARF2_FRAME_REG_OUT before, but it seems to implement a suggestion I > made in the ppc64 discussion. Now that it's there I really think you > should consider using it for hppa/hppa64 too. Something like > > #define DWARF2_FRAME_REG_OUT(REGNO, FOR_EH) \ > ((FOR_EH) ? (REGNO) : DBX_REGISTER_NUMBER (REGNO) > > if pa32-reg.h and pa64-reg.h should be enough. > > Meanwhile, I should get busy and implement the necessary support in > gdb to cope with the fact that .debug_frame has a different encoding > than .eh_frame. Let me understand, are you saying that .debug_frame has a mix of gcc and dbx register numbers at present (i.e., it contains both cfi and non-cfi data)? If that's the case and it's hard for gdb to tell the difference, then I agree that we should make the above change. Dave -- J. David Anglin dave.anglin@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602)