From owner-freebsd-toolchain@FreeBSD.ORG Tue Jan 7 19:25:54 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAC68F9C; Tue, 7 Jan 2014 19:25:54 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 70DA315D5; Tue, 7 Jan 2014 19:25:54 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id j15so414134qaq.11 for ; Tue, 07 Jan 2014 11:25:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=47Zg3Cf+BJuV3w1zSMi14rWZYgpoMvDmFzbeWUjdyWM=; b=av0GjoehlvOakClkrBoeI0ekpOsDRbJLljMv/31SrOuLs0nhNb2aFquIL4ZT2bRSF3 YgOXK04Qtnn3RB143vFa3kGTil/5HKAcs+DsjUImDR0dDDZV89vB1/dqYhCp4MQoxhw+ n3ZAtH7jh3Hm7E/vqNOeAb5UV7YDMUI95RR4/3Ya4n3pjhJHASprZDMARAAToJagZ5Y+ 7z05ppiqmajsFheW4eEf4JBiywwvqHIkZ2RIve1ajXcU3CP3L2DKZZHmMnbLBkd+xA2T rEHaZI6Tlz3pDYsUdGHvyhU71lGStvZLvH6WUp8Z/vQQpWdcYOIG2GBzehqjQ6GAXGEo 91YQ== MIME-Version: 1.0 X-Received: by 10.224.65.135 with SMTP id j7mr70922426qai.10.1389122753577; Tue, 07 Jan 2014 11:25:53 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.224.134.196 with HTTP; Tue, 7 Jan 2014 11:25:53 -0800 (PST) In-Reply-To: <6437A7D3-BB89-4FE6-B44F-46AE4E129F74@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> <6437A7D3-BB89-4FE6-B44F-46AE4E129F74@FreeBSD.org> Date: Tue, 7 Jan 2014 14:25:53 -0500 X-Google-Sender-Auth: Z4_ZVa0s1QGMzlPxrBlZlI64vv4 Message-ID: Subject: Re: [CFT] Update to clang 3.4 From: Ed Maste To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Dimitry Andric , freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 19:25:55 -0000 On 7 January 2014 03:54, David Chisnall wrote: > On 7 Jan 2014, at 06:49, Rui Paulo wrote: >> Our libdwarf was a from scratch implementation and we never used the LGP= L libdwarf. I don't know if it's worth investing time upgrading our BSD li= cenced libdwarf or importing the LGPL libdwarf. Given the push to keep the= tree mostly BSD licenced, I would say the former. I think bringing in a later version of elftoolchain / libdwarf would be straightforward. It seems there would be a fair amount of work left even after doing that though. Specifically, there's a todo item for "Add support for DWARF4 ".debug_types" section": sourceforge.net/apps/trac/elftoolchain/ticket/408. There's still ongoing development in elftoolchain, but I have no idea how likely it is that a usable libdwarf will appear in the near future. Perhaps kaiw@ or jkoshy@ can comment. > LLVM now has fairly complete DRAWF4 parsing support. What interfaces do = the ctf tools need, and are they the only consumers of libdwarf? The ctf tools are indeed the only consumers of libdwarf, and all use is in one file: cddl/contrib/opensolaris/tools/ctf/cvt/dwarf.c. It looks like it just parses various DW_TAG types (array, enum, pointer, ...) from .debug_info, and migrating to an LLVM DWARF parser wouldn't be overly difficult.