From owner-freebsd-current@FreeBSD.ORG  Fri Nov 16 10:54:13 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 94F19856;
 Fri, 16 Nov 2012 10:54:13 +0000 (UTC)
 (envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
 by mx1.freebsd.org (Postfix) with ESMTP id 347F78FC12;
 Fri, 16 Nov 2012 10:54:12 +0000 (UTC)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
 by kabab.cs.huji.ac.il with esmtp
 id 1TZJYo-0009eF-CR; Fri, 16 Nov 2012 12:54:10 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: compiler info in kernel identification string
In-reply-to: <50A612F9.30509@FreeBSD.org>
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> 
 <50A612F9.30509@FreeBSD.org>
Comments: In-reply-to Andriy Gapon <avg@FreeBSD.org>
 message dated "Fri, 16 Nov 2012 12:18:33 +0200."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Nov 2012 12:54:09 +0200
From: Daniel Braniss <danny@cs.huji.ac.il>
Message-ID: <E1TZJYo-0009eF-CR@kabab.cs.huji.ac.il>
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:54:13 -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

this does not guarantee uniformity, just look at the output it produces and 
you will see
different compilers/assemblers/scripts/flags

> 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'.
Dimitry wrote that he will handle it :-)

> 
> Besides, when I see a bug report with a dmesg *I* want to immediately know what
> compiler was used there.
today it's clang vs. gcc -- transition time --, but again it's only part of 
the story,
and soon it will only be noise.

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