From owner-freebsd-toolchain@FreeBSD.ORG Sun Jan 5 04:36:13 2014 Return-Path: Delivered-To: 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 C379C4D7 for ; Sun, 5 Jan 2014 04:36:13 +0000 (UTC) Received: from nm10-vm0.bullet.mail.bf1.yahoo.com (nm10-vm0.bullet.mail.bf1.yahoo.com [98.139.213.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6BA1EE2 for ; Sun, 5 Jan 2014 04:36:13 +0000 (UTC) Received: from [98.139.212.149] by nm10.bullet.mail.bf1.yahoo.com with NNFMP; 05 Jan 2014 04:36:06 -0000 Received: from [98.139.213.8] by tm6.bullet.mail.bf1.yahoo.com with NNFMP; 05 Jan 2014 04:36:06 -0000 Received: from [127.0.0.1] by smtp108.mail.bf1.yahoo.com with NNFMP; 05 Jan 2014 04:36:06 -0000 X-Yahoo-Newman-Id: 998124.44414.bm@smtp108.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: _msANjkVM1mnUhHAZOzByVzT46V1OEkf4Bz6eVk1f8IBFHq MpfaUA1WJmF9tVYSznilMDVHUtOir1xeaG8opEVn9VYODjtGClNkO8JfNX6D 9.GYiXqX9ixl1RMJB19Gxh1NHgX1c92LiErEWVqMH1GhHokhiUgnpvcLIeje NSITyQJiErT4w8rQ1NhaKiPyeNVCcSHz1jjjSfoFqudPToMk5pHS2.dGDmAz xxZUoLGgELUWZwPDXkgR8n7TXh3hSTaAvfOKiTtRHy0iNuOSsLPfA0mJBpaQ 0tPqS1Af85bgHWI7CFXtzy0rSp_h3f8q_QWCav4f27S3.RxP5WW_xTSKKt_L wlO9FBu0rUqatecoeTHgKBHJmVUcGHhn26oXjjSN30.RV5iNoZojEyPd8CS2 Q306Ic4zb.BiGwbws4DNViZj3QRthASmvfPs5gB7fyfJtTnKEnPHWAfDkILV 4GQcKiSlNjGGbdqemqmNw6pNsx2Ci5l4K2vyGVd73cwGKtO0mx_3E8HpuRx4 vxkaK8.hgcH6RcU3mpCazCk4BQguA0U6sB8Epqfhugf_HeG6KS9G3QmThDPp 63iqP55xGgtPwQSwTjDdPgiDY4_E8ID9kkwsA1QvJpGOGrz1IDunc1z59KRd 8bGvLG3WCRW7Ulzm.nbA5bOGmJaIuVlCXWMvbhlHYg8D8fLH9xcD3s3R7Cuj N1owT2usj1VA6SJyEzvnAq5n8pFcQlv6Ta052ooCXc_M_IOYOYQ0zcRtUj11 vonFWeJ_aOGWtlRTwPyrJffVAJ.c7tdHHtA-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf X-Rocket-Received: from [192.168.0.102] (pfg@190.157.126.109 with plain [98.139.211.125]) by smtp108.mail.bf1.yahoo.com with SMTP; 04 Jan 2014 20:36:05 -0800 PST Message-ID: <52C8E129.3030106@FreeBSD.org> Date: Sat, 04 Jan 2014 23:35:53 -0500 From: Pedro Giffuni Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: David Chisnall Subject: Re: Apple's GCC 42 enhancements (was Re: [CFT] Experimental gcc update). References: <528A924A.8050904@FreeBSD.org> <529127F8.5080606@FreeBSD.org> <3826345B-E783-43C7-B4AB-A05C95C1A8A2@FreeBSD.org> <52C5CA79.90706@FreeBSD.org> <52C88FDD.7090701@FreeBSD.org> In-Reply-To: <52C88FDD.7090701@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: 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: Sun, 05 Jan 2014 04:36:14 -0000 El 04/01/2014 5:49 p. m., Pedro Giffuni escribió: > On 02.01.2014 16:48, David Chisnall wrote: >> On 2 Jan 2014, at 20:22, Pedro Giffuni wrote: >> >>> The behaviour is consistent with llvm-gcc though, as explained here: >>> >>> https://bugs.launchpad.net/ubuntu/+source/llvm-gcc-4.2/+bug/483679 >>> >>> " looking at the LLVM/Clang documentation >>> (http://clang.llvm.org/doxygen/InitPreprocessor_8cpp-source.html) >>> shows that __block is not actually a keyword, but a macro that is >>> defined to be __attribute__((__blocks__(byref)))." >>> >>> Not sure what to do about it, I had added a #define for it in Block.h >>> since you have to link with -lBlocksRuntime anyways, but not >>> everything includes Block.h (surely not the libdispatch tests). >> Probably the best solution is to put this in cdefs.h: >> >> #if defined(__BLOCKS__) && !defined(__block) >> # define __block __attribute__((__blocks__(byref))) >> #endif >> >> (With the indentation changed to make it harder to read, as per >> style(9)). I believe __BLOCKS__ is supported by clang, although >> testing for it is discouraged in favour of the >> __has_{feature,extension} mechanism. > > Thank you for the hint. Is there some way to have this happen > only for our GCC-4.2.1 but not for clang or newer gcc? > Bah, nevermind ... it should work just fine. Feel free to go ahead though, I don't want to play with the style on that particular file ;-). > I am getting ready to commit the blocks support [1] but we can > leave the macro magic for later, while there is some consensus > on the dark arts involved ;). > Committed as r260311. I am hoping to see a lot more uses of blocks/GCD in the base system now :). Pedro. From owner-freebsd-toolchain@FreeBSD.ORG Sun Jan 5 12:06:19 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BA78491; Sun, 5 Jan 2014 12:06:19 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c: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 F32821960; Sun, 5 Jan 2014 12:06:18 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id x13so14937510wgg.19 for ; Sun, 05 Jan 2014 04:06:17 -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; bh=boZPc2f7x9RlFZsMjLhaWuRfPMKYrWTRqdh1Ec9zGmA=; b=Gql3axKogNjld5UWc9vROcnmVxu2yqneUeJpOCfzjPeOOZO2EWQD7tGn/p//KVuZAQ zYHoEcMlHy9ylz93rDSRHkOkhV0HXpmNme0McOdhW5Ob6z5GKhYGWu5Te6oQWYgvQku9 FWXopQ6k2t1UimmzH6xa59s1CrRv9fvp1wCVnqaNUo5qwHF/SsRaSypkYLZEo313B8/K licsEr1Q+/X+mV6gY2JzPmVJg1IuNoEWFyLvlALtLzHnvEDUAjp1njkQbh0q4mjIvJmy vXs+GrbZux89CWVYZEHgIH3nNbf7Ya7YHBEeVh9Y7FR+TlXN3nw0gJFf80Fevp1IMuX3 43Ww== MIME-Version: 1.0 X-Received: by 10.194.2.70 with SMTP id 6mr50327308wjs.25.1388923577359; Sun, 05 Jan 2014 04:06:17 -0800 (PST) Sender: edschouten@gmail.com Received: by 10.216.49.73 with HTTP; Sun, 5 Jan 2014 04:06:17 -0800 (PST) In-Reply-To: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> Date: Sun, 5 Jan 2014 13:06:17 +0100 X-Google-Sender-Auth: rvvLj8c3n9aQe5vlsd7aT-3FM3g Message-ID: Subject: Re: [CFT] Update to clang 3.4 From: Ed Schouten To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 Cc: 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: Sun, 05 Jan 2014 12:06:19 -0000 Hi Dimitry, 2014/1/1 Dimitry Andric : > Another important new issue is that clang 3.4 now outputs DWARF4 as > default format when using -g. Our ancient version of gdb in base does > not support this, so you must either install the gdb port, or build lldb > and use it (very experimental at this time!). Would it make sense to just change our copy of Clang to emit DWARF2 when using -g? People expect that -g emits something that can be used by our shipped version of gdb. -- Ed Schouten From owner-freebsd-toolchain@FreeBSD.ORG Sun Jan 5 13:00:40 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 9670F5FD; Sun, 5 Jan 2014 13:00:40 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 523A81E05; Sun, 5 Jan 2014 13:00:40 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::3c23:d7b2:13bc:a7ca] (unknown [IPv6:2001:7b8:3a7:0:3c23:d7b2:13bc:a7ca]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9FC755C43; Sun, 5 Jan 2014 14:00:36 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_7399F1A6-F0A0-435A-9444-93C083C2727E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: [CFT] Update to clang 3.4 From: Dimitry Andric In-Reply-To: Date: Sun, 5 Jan 2014 14:00:03 +0100 Message-Id: <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> To: Ed Schouten X-Mailer: Apple Mail (2.1827) Cc: 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: Sun, 05 Jan 2014 13:00:40 -0000 --Apple-Mail=_7399F1A6-F0A0-435A-9444-93C083C2727E Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 05 Jan 2014, at 13:06, Ed Schouten wrote: > 2014/1/1 Dimitry Andric : >> Another important new issue is that clang 3.4 now outputs DWARF4 as >> default format when using -g. Our ancient version of gdb in base does >> not support this, so you must either install the gdb port, or build lldb >> and use it (very experimental at this time!). > > Would it make sense to just change our copy of Clang to emit DWARF2 > when using -g? People expect that -g emits something that can be used > by our shipped version of gdb. There are multiple problems with that: first of all, it changes the upstream defaults, which I am very reluctant to do. Upstream actually wants to get rid of older DWARF support, since that makes their code needlessly complicated, and the rest of the world has long since moved on to newer DWARF versions. Even gcc defaults to DWARF4 now. Second, the shipped version of gdb in our tree is very old, and is basically unmaintained. Nobody in their right mind should ever use it for debugging, unless they have no other choice. As soon as the in-tree version of lldb is in workable state, we should get rid of the base gdb. I think the only tricky task left is our custom kgdb hacks, which must be ported to some newer version of gdb soon, or preferably to lldb. I have no idea if anybody is working on those. Last but not least, I can build a kernel with -gdwarf-2, but ctfconvert and/or ctfmerge still have some trouble correctly converting and/or merging the debug information to CTF. So there is something broken in either the DWARF2 output, or there is a problem in ctfconvert and ctfmerge. I need some assistance with this, from somebody who knows exactly how CTF and DTrace work together. Our CTF tools use libdwarf in base, which is also quite old, and seems to be largely unmaintained. It does not seem to support anything beyond DWARF2. I think it would be worthwhile to upgrade this library from upstream ASAP. -Dimitry --Apple-Mail=_7399F1A6-F0A0-435A-9444-93C083C2727E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlLJV2AACgkQsF6jCi4glqPaBwCfSspAomAXe/zZC7hPDjIBfFBb 4j8AnAhCbXFWzv2Kw9fuW9PuCCC6bnRa =j9iq -----END PGP SIGNATURE----- --Apple-Mail=_7399F1A6-F0A0-435A-9444-93C083C2727E-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Jan 7 06:49:27 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 3F9D5F53; Tue, 7 Jan 2014 06:49:27 +0000 (UTC) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id 288F016D9; Tue, 7 Jan 2014 06:49:26 +0000 (UTC) Received: from [10.0.1.3] (c-24-6-115-18.hsd1.ca.comcast.net [24.6.115.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id 8351239827; Mon, 6 Jan 2014 22:49:19 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: [CFT] Update to clang 3.4 From: Rui Paulo In-Reply-To: <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> Date: Mon, 6 Jan 2014 22:49:18 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1827) Cc: 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 06:49:27 -0000 On 5 Jan 2014, at 05:00, Dimitry Andric wrote: > I need some assistance with this, from somebody who knows exactly how > CTF and DTrace work together. Our CTF tools use libdwarf in base, = which > is also quite old, and seems to be largely unmaintained. It does not > seem to support anything beyond DWARF2. I think it would be = worthwhile > to upgrade this library from upstream ASAP. 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. -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Tue Jan 7 08:55:09 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 18C80F88; Tue, 7 Jan 2014 08:55:09 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8F5110F5; Tue, 7 Jan 2014 08:55:05 +0000 (UTC) Received: from [192.168.0.7] (cpc28-cmbg15-2-0-cust64.5-4.cable.virginm.net [86.27.189.65]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id s078t09a042715 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jan 2014 08:55:02 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: [CFT] Update to clang 3.4 From: David Chisnall In-Reply-To: Date: Tue, 7 Jan 2014 08:54:55 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <6437A7D3-BB89-4FE6-B44F-46AE4E129F74@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> To: Rui Paulo X-Mailer: Apple Mail (2.1822) Cc: freebsd-toolchain@FreeBSD.org, Dimitry Andric 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 08:55:09 -0000 On 7 Jan 2014, at 06:49, Rui Paulo wrote: > On 5 Jan 2014, at 05:00, Dimitry Andric wrote: >=20 >> I need some assistance with this, from somebody who knows exactly how >> CTF and DTrace work together. Our CTF tools use libdwarf in base, = which >> is also quite old, and seems to be largely unmaintained. It does not >> seem to support anything beyond DWARF2. I think it would be = worthwhile >> to upgrade this library from upstream ASAP. >=20 > 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. LLVM now has fairly complete DRAWF4 parsing support. What interfaces do = the ctf tools need, and are they the only consumers of libdwarf? David 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. From owner-freebsd-toolchain@FreeBSD.ORG Tue Jan 7 19:37:08 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 499D7620; Tue, 7 Jan 2014 19:37:08 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EAAF31687; Tue, 7 Jan 2014 19:37:07 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id i8so579800qcq.35 for ; Tue, 07 Jan 2014 11:37:07 -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; bh=pZaaU6jD8Chuk0Z8T6mn0H90YVZpKjeJjLSAQSbvWks=; b=kfCe2MC0FJuzJ5foLBZ7pm4Nv7cJZOOyi0PSbq/P45MzJDJrLFj1WdxEbi7Blntrgd LsZDiP0Mc8VgzT75/tE7bbbkeopckaAb2AP6kWfemsEMPOkax4IZKOp1e/2Uq99elMAW eVvtQFK7/lu7K7fOgQT1cZBZfQQZwd122hdoQuahCOjP05siIxe/d+GgYlTr39anfBW7 eWsc4o5MYlhcCudoXE2GXtaNVXsusvP4e/LP1io7qcBWuygMiPO5+oD0xvToBzisapPP LMkR6uFwPIwV60PdITGY6i3+ZIWAjcG+BpwMOSCyGmeNhQMpY76w1LvxGrD4EaVDTPMV 4+Gg== MIME-Version: 1.0 X-Received: by 10.49.34.207 with SMTP id b15mr199312406qej.49.1389123427039; Tue, 07 Jan 2014 11:37:07 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.224.134.196 with HTTP; Tue, 7 Jan 2014 11:37:06 -0800 (PST) In-Reply-To: <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> References: <541C998A-071A-4917-9D91-DD00CB0E2689@FreeBSD.org> <29C2D69E-9EC8-418D-A333-FC1A8DA2133B@FreeBSD.org> Date: Tue, 7 Jan 2014 14:37:06 -0500 X-Google-Sender-Auth: 79OzlyysCF_lGjaO-BKUNk31vMY Message-ID: Subject: Re: [CFT] Update to clang 3.4 From: Ed Maste To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Cc: 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:37:08 -0000 On 5 January 2014 08:00, Dimitry Andric wrote: > > Second, the shipped version of gdb in our tree is very old, and is > basically unmaintained. Nobody in their right mind should ever use it > for debugging, unless they have no other choice. As soon as the in-tree > version of lldb is in workable state, we should get rid of the base gdb. > > I think the only tricky task left is our custom kgdb hacks, which must > be ported to some newer version of gdb soon, or preferably to lldb. I > have no idea if anybody is working on those. Our in-tree gdb is not particularly useful, but it also supports some debug information that both the ports gdb and upstream gdb do not. I am unaware of anyone working on bringing those changes and kgdb support to the ports gdb; I don't expect I'll be able to. I will work on LLDB kernel debugging support although I don't have a specific timeline yet.