From owner-freebsd-current@FreeBSD.ORG  Fri Nov 16 10:19:01 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 5608DF95;
 Fri, 16 Nov 2012 10:19:01 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 4DC4F8FC12;
 Fri, 16 Nov 2012 10:19:00 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA14363;
 Fri, 16 Nov 2012 12:18:35 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1TZJ0M-000196-Tv; Fri, 16 Nov 2012 12:18:34 +0200
Message-ID: <50A612F9.30509@FreeBSD.org>
Date: Fri, 16 Nov 2012 12:18:33 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:16.0) Gecko/20121030 Thunderbird/16.0.2
MIME-Version: 1.0
To: Daniel Braniss <danny@cs.huji.ac.il>
Subject: Re: compiler info in kernel identification string
References: <20121113234303.GA15319@dft-labs.eu> <50A3639C.9050200@FreeBSD.org>
 <1352907497.1217.147.camel@revolution.hippie.lan>
 <50A57623.4020108@FreeBSD.org> <50A5EC7C.5050303@FreeBSD.org>
 <5B4DE1FD-5DD3-49A5-B8DB-6D4C03ABD742@cederstrand.dk>
 <50A606E7.5000302@FreeBSD.org> <E1TZIix-0008lm-Al@kabab.cs.huji.ac.il>
In-Reply-To: <E1TZIix-0008lm-Al@kabab.cs.huji.ac.il>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>,
 Mateusz Guzik <mjguzik@gmail.com>, Dimitry Andric <dim@FreeBSD.org>,
 Erik Cederstrand <erik@cederstrand.dk>, freebsd-current@FreeBSD.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 10:19:01 -0000


This is starting to turn into a bikeshed, but anyway...

on 16/11/2012 12:00 Daniel Braniss said the following:
> the question as to what compiler was used to compile the kernel is a bit of an
> oxymoron, since the kernel is made up of many different modules, which get 
> compiled
> either by different compilers, or different compiler flags.

The canonical way to compile a kernel is to use buildkernel and compile modules
along with the kernel.  Other configurations are supported too, of course.

> since the compiler does 'sign' the modules it compiles (and clang will/should
> do it soon: http://llvm.org/bugs/show_bug.cgi?id=7292) some tool like
> file(1) could be modified to provide it, or config -x (8) ...

The key word in your note about clang is 'soon' as in 'not yet'.

Besides, when I see a bug report with a dmesg *I* want to immediately know what
compiler was used there.

> IMHO, the only meaningfull information added to uname was the svn/git(and 
> hopefully hg) rev. version.


-- 
Andriy Gapon