Date: Thu, 3 Jun 2010 19:38:45 -0500 From: Mark Linimon <linimon@lonesome.com> To: Alban Hertroys <dalroi@solfertje.student.utwente.nl> Cc: Kostik Belousov <kostikbel@gmail.com>, Roman Divacky <rdivacky@freebsd.org>, current@freebsd.org Subject: Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD Message-ID: <20100604003845.GE22064@lonesome.com> In-Reply-To: <338E3C69-1542-4F0D-89C4-C96EA3575AEA@solfertje.student.utwente.nl> References: <20100529130240.GA99732@freebsd.org> <20100530135859.GI83316@deviant.kiev.zoral.com.ua> <508DA8CE-749A-46B4-AF0B-392DB08CBBCD@samsco.org> <20100531095617.GR83316@deviant.kiev.zoral.com.ua> <338E3C69-1542-4F0D-89C4-C96EA3575AEA@solfertje.student.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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. The latter number seems kind of low right now, but that's probably because some of them are now obscured by BROKEN tags: http://portsmon.freebsd.org/portsconcordanceforbuilderror.py?build_error=gcc_bug 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 I don't have any statistic for "produces bad code". mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100604003845.GE22064>