From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 968 invoked by alias); 5 Sep 2003 09:50:51 -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 780 invoked from network); 5 Sep 2003 09:50:41 -0000 Received: from unknown (HELO cam-admin0.cambridge.arm.com) (193.131.176.54) by sources.redhat.com with SMTP; 5 Sep 2003 09:50:41 -0000 Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id KAA23077; Fri, 5 Sep 2003 10:50:23 +0100 (BST) Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h859oNV23553; Fri, 5 Sep 2003 10:50:23 +0100 Message-Id: <200309050950.h859oNV23553@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: Daniel Jacobowitz cc: Richard.Earnshaw@buzzard.freeserve.co.uk, gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Re: [RFA] Repost ARM frame patches In-reply-to: Your message of "Wed, 03 Sep 2003 16:41:40 EDT." <20030903204139.GA9605@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Sep 2003 09:50:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-09/txt/msg00057.txt.bz2 > On Tue, Sep 02, 2003 at 11:52:26PM +0100, Richard Earnshaw wrote: > > Daniel, > > > > My appologies for not reviewing this before. Just way too much day job... > > > > It looks fine to me (at least, it seems better than what's there at > > present). > > > > My only question is, once we start using the dwarf2 unwinder, can it cope > > with the fact that gcc currently does not emit frame unwind information > > for Thumb code? (ie can it handle a mix of code that uses dwarf2 and > > traditional unwinding?) > > I was going to say yes, but... > > drow@nevyn:/big/fsf/projects/arm/obj/gdb/testsuite/interwork% readelf -wf test1.o > The section .debug_frame contains: > > 00000000 0000000c ffffffff CIE > Version: 1 > Augmentation: "" > Code alignment factor: 1 > Data alignment factor: -4 > Return address column: 14 > > DW_CFA_def_cfa: r13 ofs 0 > > 00000010 0000000c 00000000 FDE cie=00000000 pc=00000000..0000001c > > 00000020 0000000c 00000000 FDE cie=00000000 pc=0000001c..00000046 > > > i.e. GCC emits _empty_ dwarf unwind information for thumb functions, > rather than none at all. That's unlikely to work. We'd need to modify > the dwarf2 unwinder to ignore empty FDEs. > > I'll check in the non-dwarf parts now, and then we can figure out what > to do about that. Though of course a trivial leaf function *will* have an empty FDE. Consider int func(void) { return 0;} Which compiles to mov r0, #0 bx lr I would have thought that wouldn't need any frame unwind information. So we would have a problem distinguishing trivial cases from "not generated" cases. R.