Date: Tue, 11 Sep 2012 14:52:20 +0200 From: Erik Cederstrand <erik@cederstrand.dk> To: Roman Divacky <rdivacky@freebsd.org> Cc: toolchain@freebsd.org, current@freebsd.org Subject: Re: Clang as default compiler November 4th Message-ID: <848C813E-E6EC-4FAF-9374-B5583A077404@cederstrand.dk> In-Reply-To: <20120911123833.GA54483@freebsd.org> References: <20120910211207.GC64920@lor.one-eyed-alien.net> <20120911104518.GF37286@deviant.kiev.zoral.com.ua> <20120911120649.GA52235@freebsd.org> <20120911122122.GJ37286@deviant.kiev.zoral.com.ua> <20120911123833.GA54483@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Roman, Den 11/09/2012 kl. 14.38 skrev Roman Divacky <rdivacky@freebsd.org>: >=20 > Upstream developers almost never use gcc4.2.1 as we do. So right now = the > ports maintainer must check whats wrong in the case the (upgraded) = port > doesnt compile with our in-tree gcc. >=20 >=20 > It can be trivial USE_GCC=3D4.something but the burden is exactly the = same > as with clang. So can we do a sweep on the ports tree and mark the 2232 ports with = USE_GCC=3D4.2 until they can actually build with clang? This could allow = the clang switch to proceed. Hopefully, waiting for GCC to compile just = to install some tiny port will be enough of a nuisance for people to = eventually fix the remaining ports. > By the nature of "developing the OS" we are forced to use compilers = and > toolchains. Recently I saw you submitting/committing patches with = .byte > sequences because our default assembler cant handle the instructions. > I saw jhb@ updating binutils to support invept/invvpid. >=20 > In my eyes, switching to clang by default lowers the = compiler/toolchain > maintenance burden we have. I agree. Switching away from abandonware to a compiler that is actively = maintained is a good thing. Regarding performance, I could do some benchmarking in my spare time, = but it does seem like an unforgiving task. Anyone posting any benchmark = numbers on these lists is going to be tarred, feathered, forced to print = out the full GCC 4.2.1 source code, read it out loud on the town square, = and spend the next month addressing concerns from people not willing to = do the work themselves :-) Erik=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?848C813E-E6EC-4FAF-9374-B5583A077404>