From owner-freebsd-current@FreeBSD.ORG Sat Jun 5 01:27:08 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27782106566B; Sat, 5 Jun 2010 01:27:08 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id BED838FC14; Sat, 5 Jun 2010 01:27:07 +0000 (UTC) Received: by iwn5 with SMTP id 5so2081846iwn.13 for ; Fri, 04 Jun 2010 18:27:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=KOkJVBN75osgH1fJwyzTkKxamuc/+dfCHkVMOun9uUo=; b=aZ7JzmMBaq8QVlvYWaoWA6qM7SgKi7vI/vWInUUhqAou44J0qzbLKdXDVcY4Qk/6DR E5fVNU/DxJwfxPevASv9P5KWUIOuGhg789ubFQ1oEWqYnuEXTkV+8ejLcNtsYIkO94Xc Mo6rPlRo1bkeOwO60QTVcys/lQRZGjUsWr16c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=sBjWaIL3gIfTSjMdhR2UNq29HV9vCDtdzZXD6kwHEgbafew0e6Qaff1S0RTEJex67H E/7NyYvBeGMe6sVnU4SoeMfx19aq++Oux1nNzHSx7vovh7k+fs4r2AzLtegZHqem41zX gXIxDsk0klXKhKwDFMjBpVJ+KtrwgIrCUZpeE= Received: by 10.231.147.143 with SMTP id l15mr1830355ibv.9.1275701226793; Fri, 04 Jun 2010 18:27:06 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-128-180.dsl.klmzmi.sbcglobal.net [99.181.128.180]) by mx.google.com with ESMTPS id d9sm7915558ibl.4.2010.06.04.18.27.05 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Jun 2010 18:27:06 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C09A7E8.10503@dataix.net> Date: Fri, 04 Jun 2010 21:27:04 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100515 Thunderbird MIME-Version: 1.0 To: Doug Barton References: <20100604152605.GA80277@freebsd.org> <4C0930E3.3030301@FreeBSD.org> In-Reply-To: <4C0930E3.3030301@FreeBSD.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Roman Divacky , current@freebsd.org Subject: Re: [INFO]: import of clang/LLVM to happen on June 9th X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2010 01:27:08 -0000 On 06/04/2010 12:59, Doug Barton wrote: > On 06/04/10 08:26, Roman Divacky wrote: >> Dear current@ >> >> On June 9th, we are importing clang/LLVM into FreeBSD HEAD. > > Excellent news! :) I am in favor of this, and look forward to a day of > using a FreeBSD system compiled as much as possible with clang. > > During the ongoing discussion there were 2 items identified that I was > particularly interested in, and I personally would like to see those > items resolved before the clang import: > > 1. Have uname report the compiler (and compiler version?) that the > kernel was compiled with. This can likely be done through newvers.sh > easily enough. IMHO, With all due respect, Adding CLANG to uname ? This would only leave it to be useless information later on when we finally jettison gcc out of base. How about this. Create a sysctl kern.compilers and set it to be a read only. Assign a value system to the compilers that can be used. 1 = gcc 3 = clang/llvm 5 = other 4 = gcc+clang 6 = gcc+other 8 = clang+other 9 = one strange environment. etc... etc... etc... Then you can still have newvers.sh generate something for inclusion that would set the final value of that sysctl. > > 2. Publish instructions on how to set up a different compiler for ports. This should not stop the import. > > I realize that what you're talking about in this announcement is simply > importing clang into the build, not using it to build anything yet. > However my concern is that if we don't attend to these 2 issues sooner > than later that they will get lost in the shuffle. > > In any case, congratulations on the progress the clang team has made so > far, and on this new milestone. :) > > > Doug > Regards, -- jhell