On 4 June 2010 12:52, Andriy Gapon <avg_at_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 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. > AFAIK, NetBSD does it for quite a while since they have a different pov on this. http://www.thejemreport.com/content/view/317 -- wbr, pluknetReceived on Fri Jun 04 2010 - 07:32:09 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:04 UTC