Date: Tue, 7 Jan 2014 14:25:53 -0500 From: Ed Maste <emaste@freebsd.org> To: David Chisnall <theraven@freebsd.org> Cc: Dimitry Andric <dim@freebsd.org>, freebsd-toolchain@freebsd.org Subject: Re: [CFT] Update to clang 3.4 Message-ID: <CAPyFy2Bnpha=%2B49E%2BrL0Rd=TKtgOybGQAtOWE8m5sPCNiT5_Pw@mail.gmail.com> In-Reply-To: <6437A7D3-BB89-4FE6-B44F-46AE4E129F74@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> <CAJOYFBAf6rsZvNKgm5O-_rS%2BR5c=7939A3THNXanVSHVMnZcog@mail.gmail.com> <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> <C72E6B85-C203-42F3-B27C-4B981A60460E@FreeBSD.org> <6437A7D3-BB89-4FE6-B44F-46AE4E129F74@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 January 2014 03:54, David Chisnall <theraven@freebsd.org> wrote: > On 7 Jan 2014, at 06:49, Rui Paulo <rpaulo@FreeBSD.org> wrote: >> Our libdwarf was a from scratch implementation and we never used the LGPL libdwarf. I don't know if it's worth investing time upgrading our BSD licenced 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Bnpha=%2B49E%2BrL0Rd=TKtgOybGQAtOWE8m5sPCNiT5_Pw>