From owner-freebsd-toolchain@FreeBSD.ORG Mon Aug 6 12:16:43 2012 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24C04106564A for ; Mon, 6 Aug 2012 12:16:43 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from csmtp2.one.com (csmtp2.one.com [91.198.169.22]) by mx1.freebsd.org (Postfix) with ESMTP id D5E918FC14 for ; Mon, 6 Aug 2012 12:16:42 +0000 (UTC) Received: from [192.168.1.12] (unknown [176.222.238.90]) by csmtp2.one.com (Postfix) with ESMTPA id B72EA3042C15; Mon, 6 Aug 2012 12:16:29 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Erik Cederstrand In-Reply-To: <9F286684-EA0B-4F6F-8C1F-0036DF9A0C53@bsdimp.com> Date: Mon, 6 Aug 2012 14:16:29 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9F286684-EA0B-4F6F-8C1F-0036DF9A0C53@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1278) Cc: freebsd-toolchain@freebsd.org, David Chisnall Subject: Re: BSD archive file formats X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Aug 2012 12:16:43 -0000 Den 03/08/2012 kl. 17.55 skrev Warner Losh: > Hi Pete, >=20 > the best way to find out if support for archives are needed is to = release it for testing. People find the craziest things when testing in = a wider arena. To do that, it would be helpful if our LLVM is updated to something = later than r160433, since our version in CURRENT needs patching for = MCLinker to work. I've asked dim@, but no reply yet. As far I know, we = try to follow official LLVM releases in CURRENT. In that case, I guess = LLVM 3.2 will happen around December 2012. Thanks, Erik From owner-freebsd-toolchain@FreeBSD.ORG Mon Aug 6 12:44:29 2012 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9A6C1065673 for ; Mon, 6 Aug 2012 12:44:29 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9BD7E8FC1B for ; Mon, 6 Aug 2012 12:44:29 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:3d5b:6e64:5e1b:e5fd] (unknown [IPv6:2001:7b8:3a7:0:3d5b:6e64:5e1b:e5fd]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1D3C55C37; Mon, 6 Aug 2012 14:44:28 +0200 (CEST) Message-ID: <501FBC2B.70906@FreeBSD.org> Date: Mon, 06 Aug 2012 14:44:27 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Erik Cederstrand References: <9F286684-EA0B-4F6F-8C1F-0036DF9A0C53@bsdimp.com> In-Reply-To: X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@freebsd.org, David Chisnall Subject: Re: BSD archive file formats X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Aug 2012 12:44:30 -0000 On 2012-08-06 14:16, Erik Cederstrand wrote: ... > To do that, it would be helpful if our LLVM is updated to something later than r160433, since our version in CURRENT needs patching for MCLinker to work. I've asked dim@, but no reply yet. As far I know, we try to follow official LLVM releases in CURRENT. In that case, I guess LLVM 3.2 will happen around December 2012. I'm working on importing a new clang snapshot (from trunk, so version 3.2), on request from Brooks and others. It's going to take a little while, though. This is not because it is tricky to import it into the tree as-is, but because this new version triggers a whole bunch of new warnings, that I have to verify the fixes for with several people. :) Fur -current, I see no big trouble with using a snapshot, as long as it is reasonably stable. That is, it must be able to build itself flawlessly, survive all of llvm and clang's own regression tests, and obviously, build world, kernel and a reasonable set of ports. That said, I do remember you asked me to import a specific changelist from upstream to make MCLinker build. I will do so tonight, probably.