Date: Fri, 04 Jun 2010 11:52:44 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: bf1783@gmail.com Cc: freebsd-current@FreeBSD.org Subject: Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD Message-ID: <4C08BEDC.7010807@icyb.net.ua> In-Reply-To: <AANLkTilBgX9gACP0luWAk2hQDCmp_pyAW_Dye85-6TOg@mail.gmail.com> References: <AANLkTilBgX9gACP0luWAk2hQDCmp_pyAW_Dye85-6TOg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C08BEDC.7010807>