Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jun 2010 11:38:09 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Lawrence Stewart <lstewart@freebsd.org>
Cc:        Roman Divacky <rdivacky@freebsd.org>, "James R. Van Artsdalen" <james-freebsd-current@jrv.org>, current@freebsd.org
Subject:   Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD
Message-ID:  <20100601083809.GF83316@deviant.kiev.zoral.com.ua>
In-Reply-To: <4C04587E.70800@freebsd.org>
References:  <20100529130240.GA99732@freebsd.org> <20100530135859.GI83316@deviant.kiev.zoral.com.ua> <508DA8CE-749A-46B4-AF0B-392DB08CBBCD@samsco.org> <4C04456D.7080408@jrv.org> <4C04587E.70800@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--nQeUMoeVp7j9rzTQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 01, 2010 at 10:46:54AM +1000, Lawrence Stewart wrote:
> On 06/01/10 09:25, James R. Van Artsdalen wrote:
> [snip interesting history]
>=20
> >I do suggest modifying the FreeBSD build process so that uname -a shows
> >the compiler and its version for both the kernel and userland.
>=20
> Reading through this discussion, I wanted to draw attention to this=20
> footnote in James' email. It sounds like a sensible and useful=20
> suggestion that would go some way to addressing Kostik's concerns about=
=20
> knowing whether a kernel bug report was related to a gcc or clang built=
=20
> kernel.

This is unsufficient. What could work is if clang provided some common
symbol into all .o files generated by it, e.g. __clang_compiled. And
then kernel considered tainted with corresponding banner printed when
weak reference to that symbol is resolved to non-zero. This does not
handle modules and does not cleanly handle usermode runtime (libc,
libthr, rtld etc).

I do not care about users busting their systems by using alternative
compilers and/or mixed builds. I worry about wasting developers time
chasing bugs that are not bugs in the FreeBSD system. As an example
see low-visible thread about sig11 during buildworld.

--nQeUMoeVp7j9rzTQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAkwExvEACgkQC3+MBN1Mb4jzLgCbBgpicmmSqKkO/tuDf9rHI4Qp
NpkAoNx6X1W2AojXJUNVZn4wvzNvBflZ
=Qky7
-----END PGP SIGNATURE-----

--nQeUMoeVp7j9rzTQ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100601083809.GF83316>