From owner-freebsd-current@FreeBSD.ORG Wed Nov 14 09:25:49 2012 Return-Path: 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 F3B44CBB; Wed, 14 Nov 2012 09:25:48 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id AD9028FC18; Wed, 14 Nov 2012 09:25:48 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6] (unknown [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 244EE5C59; Wed, 14 Nov 2012 10:25:46 +0100 (CET) Message-ID: <50A3639C.9050200@FreeBSD.org> Date: Wed, 14 Nov 2012 10:25:48 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Mateusz Guzik , freebsd-current@freebsd.org, avg@freebsd.org Subject: Re: compiler info in kernel identification string References: <20121113234303.GA15319@dft-labs.eu> In-Reply-To: <20121113234303.GA15319@dft-labs.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 14 Nov 2012 09:25:49 -0000 On 2012-11-14 00:43, Mateusz Guzik wrote: > avg@ suggested to include compiler version in the kernel so that it's > present in uname (and one can easly tell what was used to compile it). > > Here is my attempt: > http://people.freebsd.org/~mjg/patches/newvers-compiler.diff > > Basically adds compiler name and version/revision after revision of > system sources. > > Sample output from dirty git sources: > gcc: > FreeBSD 10.0-CURRENT #7 r242962=264d569-dirty(gcc-4.2.1-20070831): Wed > Nov 14 00:11:51 CET 2012 > > clang: > FreeBSD 10.0-CURRENT #8 r242962=264d569-dirty(clang-r162107): Wed Nov 14 > 00:12:26 CET 2012 > > Sample output from svn with gcc: > FreeBSD 10.0-CURRENT #1 r243006:243007M(gcc-4.2.1-20070831): Wed Nov 14 > 00:41:23 CET 2012 > > I have no strong opinions on format, I just want this information easly > accessible. Yes, this is handy to have. Note that gcc already puts an id string into each object file it produces, but sometimes during linking, these can be stripped out... Regarding the format, I don't see the necessity of parsing the version information, which will always be very fragile. Just include the complete version string in the compiler identification, similar to what Linux does, e.g. on a CentOS box: $ gcc -v 2>&1 | grep 'version ' gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) $ dmesg | grep 'gcc version ' Linux version 2.6.32-279.2.1.el6.x86_64 (mockbuild@c6b7.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jul 20 01:55:29 UTC 2012 That way, you are sure never to lose information. This also works for gcc from ports (which is the reason for the space after 'version' in the grep command): $ gcc47 -v 2>&1 | grep 'version ' gcc version 4.7.3 20120929 (prerelease) (FreeBSD Ports Collection) I realize this is a bit long, but it is better to have complete than stripped information.