Date: Sun, 2 May 2010 23:17:00 +0300 From: Eitan Adler <eitanadlerlist@gmail.com> To: yuri@rawbw.com Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org, =?UTF-8?Q?Andrius_Mork=C5=ABnas?= <hinokind@gmail.com> Subject: Re: GSoC: Making ports work with clang Message-ID: <AANLkTin0yOPIwfeUlNKUBBdTRDqYgAMOV2VzYyYv-SIJ@mail.gmail.com> In-Reply-To: <4BDD28E2.8010201@rawbw.com> References: <op.vb0w1zrh43o42p@klevas> <4BDD28E2.8010201@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Having tried clang++ I have a feeling that it's not quite ready to be a > generic c++ compiler. > It crashes a lot, fails on many quite simple c++ patterns. Very immature. > Don't you feel it's too early to start project like you are going to given > the state of clang with c++? > You will just keep stumbling upon various problems with various ports and > maybe will make 30% of c++ ports build with it at best. Good - and those 30% of ports will help improve clang++ even more. Hopefully over time that number will increase to 100% and we will be able to say goodbye to gcc for good.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin0yOPIwfeUlNKUBBdTRDqYgAMOV2VzYyYv-SIJ>