Date: Fri, 4 Jun 2010 13:32:01 +0400 From: pluknet <pluknet@gmail.com> To: Andriy Gapon <avg@icyb.net.ua> Cc: bf1783@gmail.com, freebsd-current@freebsd.org Subject: Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD Message-ID: <AANLkTin9phZln_bHReRNjz7ERj4is0qe4lw49HwqXW2G@mail.gmail.com> In-Reply-To: <4C08BEDC.7010807@icyb.net.ua> References: <AANLkTilBgX9gACP0luWAk2hQDCmp_pyAW_Dye85-6TOg@mail.gmail.com> <4C08BEDC.7010807@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 June 2010 12:52, Andriy Gapon <avg@icyb.net.ua> wrote: > 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 bug= s >>>> 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. =A0Some 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_erro= r=3Dgcc4_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. > AFAIK, NetBSD does it for quite a while since they have a different pov on = this. http://www.thejemreport.com/content/view/317 --=20 wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin9phZln_bHReRNjz7ERj4is0qe4lw49HwqXW2G>