From owner-freebsd-current@FreeBSD.ORG  Fri Jun  4 08:13:56 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7C55A1065673
	for <freebsd-current@FreeBSD.org>; Fri,  4 Jun 2010 08:13:56 +0000 (UTC)
	(envelope-from bf1783@googlemail.com)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com
	[74.125.82.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 152208FC2B
	for <freebsd-current@FreeBSD.org>; Fri,  4 Jun 2010 08:13:55 +0000 (UTC)
Received: by mail-wy0-f182.google.com with SMTP id 28so903140wyf.13
	for <freebsd-current@FreeBSD.org>; Fri, 04 Jun 2010 01:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:mime-version:received:received:reply-to:date
	:message-id:subject:from:to:cc:content-type;
	bh=2xWFTuWErOkF5gu/f6R/GCxG71bCDwfW5HdvM8YbcR4=;
	b=V43rJOAWnDBA6ZToIhJ80dJiQS6kAtjqTb8Fj2QTnU4g50Ge7/hH0dhXfO1GosdOOH
	wP2FvH8s0PyDBT2GE8lmPGFNbAXTWG4b3QdUrVtVsF1hLt+oZSHIU3z+jN/u52DOfEEZ
	vuGQCDidGBk+EdnsnRPmgDF5Tm4h8pDGeQegk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=mime-version:reply-to:date:message-id:subject:from:to:cc
	:content-type;
	b=kZXvfd0I5co7WQsS0IQfuruE8sXvQkVNjbVhMP8Kbp6kdlTNmsxKHVeDrgcb003nYp
	YaWvmViLrhRk04BKQp9ug9KdovwmDb6BUtcKZ+BgyG1BVqCyMu2KwmBsOuCtzydp5GCx
	zILaRmAWn5zTT+sQEhnn/BpqH0pRV8LWMY34U=
MIME-Version: 1.0
Received: by 10.216.186.72 with SMTP id v50mr92441wem.50.1275639235297; Fri, 
	04 Jun 2010 01:13:55 -0700 (PDT)
Received: by 10.216.183.5 with HTTP; Fri, 4 Jun 2010 01:13:55 -0700 (PDT)
Date: Fri, 4 Jun 2010 08:13:55 +0000
Message-ID: <AANLkTilBgX9gACP0luWAk2hQDCmp_pyAW_Dye85-6TOg@mail.gmail.com>
From: "b. f." <bf1783@googlemail.com>
To: freebsd-current@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Linimon <linimon@lonesome.com>
Subject: Re: [TESTING]: ClangBSD branch needs testing before the import to 
	HEAD
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bf1783@gmail.com
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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, 04 Jun 2010 08:13:56 -0000

Mark Linimon wrote:
>On Tue, Jun 01, 2010 at 12:18:41PM +0200, Alban Hertroys wrote:
>> Compiler bugs in gcc are probably just as hard to find as compiler bugs
>> in clang
>
>There are two types of compiler bug: a) bug that produces bad code; b)
>bug that makes the compiler crash.
>

Let's remember that the entire toolchain is important here, and not
just the compiler.  Some of the problems can be attributed to our old
binutils.

>For comparison, bitrot that is probably due to older ports not keeping
>up with compiler changes is at:
>
>http://portsmon.freebsd.org/portsconcordanceforbuilderror.py?build_error=gcc4_error
>

How did you obtain "gcc4-errors"?

We're not alone here: some major GNU/Linux distributions, NetBSD, and
DragonFlyBSD are using newer versions of binutils and/or gcc, so we
can look at their patches and error logs to fix some problems.

b.