From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28183 invoked by alias); 7 Jan 2004 23:36:40 -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 27740 invoked from network); 7 Jan 2004 23:36:12 -0000 Received: from unknown (HELO localhost.redhat.com) (65.49.3.48) by sources.redhat.com with SMTP; 7 Jan 2004 23:36:12 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9964D2B8F; Wed, 7 Jan 2004 18:35:59 -0500 (EST) Message-ID: <3FFC97DF.2030009@gnu.org> Date: Wed, 07 Jan 2004 23:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: Alan Modra Cc: Mark Kettenis , gcc-patches@gcc.gnu.org, geoffk@desire.geoffk.org, dje@watson.ibm.com, gdb-patches@sources.redhat.com, Ulrich.Weigand@de.ibm.com Subject: Re: Incorrect DWARF-2 register numbers on PPC64? References: <200312182258.hBIMwgT25422@makai.watson.ibm.com> <200312201527.hBKFRHgI000712@elgar.kettenis.dyndns.org> <3FF5A069.1040306@gnu.org> <200401022317.i02NHQBR001191@desire.geoffk.org> <20040106152710.GB2533@bubble.modra.org> <200401071743.i07HhAle000811@elgar.kettenis.dyndns.org> <20040107222907.GO2533@bubble.modra.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg00183.txt.bz2 > On Wed, Jan 07, 2004 at 06:43:10PM +0100, Mark Kettenis wrote: > >> If I read your patch correctly, this fixes normal DWARF 2 debugging >> info to use the official System V register numbers, but lets GCC >> continue to use its own numbering for the Call Frame Info (CFI) in >> both the .eh_frame and .debug_frame sections. > > > That's correct. hppa, hppa64, iq2000 and ns32k all do the same. Outch! > mips and cris also define DWARF_FRAME_REGNUM, but squinting at the code > leads me to believe they will actually use the same register numbers. (same as which? gcc or dwarf 2?) > >> This won't work for GDB >> since it assumes that CFI uses the same register number encoding as >> all the other DWARF 2 debug information. > > > Hmm, I can see that a debugger might reasonably expect .debug_frame > to have the same numbers. When I wrote the patch, I was concentrating > on .eh_frame rather than .debug_frame, but .debug_frame uses the > .eh_frame numbering. It's a little perplexing that dwarf2out.c does > this, as it means defining DWARF_FRAME_REGNUM to something other > than DBX_REGISTER_NUMBER is useless. DWARF_FRAME_REGNUM ought to > just effect .eh_frame. I'm not keen on trying to untangle dwarf2out.c > though.. Is it going to be possible to get this untangled before 3.4 is branched/released? Andrew