From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 09:02:08 2010 Return-Path: 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 1E965106567A for ; Fri, 4 Jun 2010 09:02:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB6E8FC1F for ; Fri, 4 Jun 2010 09:02:04 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA29841; Fri, 04 Jun 2010 12:02:02 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OKSdx-00040s-RI; Fri, 04 Jun 2010 11:52:45 +0300 Message-ID: <4C08BEDC.7010807@icyb.net.ua> Date: Fri, 04 Jun 2010 11:52:44 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100321) MIME-Version: 1.0 To: bf1783@gmail.com References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2010 09:02:08 -0000 on 04/06/2010 11:13 b. f. said the following: > 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. DragonFlyBSD and NetBSD use newer GCC? This is the first time I hear about that. No doubt about major Linux distributions, though. -- Andriy Gapon