[TESTING]: ClangBSD branch needs testing before the import to
kostikbel at gmail.com
Tue Jun 1 08:41:39 UTC 2010
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]
> >I do suggest modifying the FreeBSD build process so that uname -a shows
> >the compiler and its version for both the kernel and userland.
> Reading through this discussion, I wanted to draw attention to this
> footnote in James' email. It sounds like a sensible and useful
> suggestion that would go some way to addressing Kostik's concerns about
> knowing whether a kernel bug report was related to a gcc or clang built
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100601/5d691b8c/attachment.pgp
More information about the freebsd-current