Date: Thu, 30 May 2013 11:11:14 -0500 From: Pedro Giffuni <pfg@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, David Chisnall <theraven@FreeBSD.org>, Rui Paulo <rpaulo@felyko.com>, Andriy Gapon <avg@FreeBSD.org> Subject: Re: [CFT] gcc: support for barcelona Message-ID: <51A77A22.3040103@FreeBSD.org> In-Reply-To: <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com> References: <51A38CBD.6000702@FreeBSD.org> <E9DC99EF-F2E9-4A5F-8370-36DA25DE2C89@felyko.com> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> <C0B4C633-EC1C-41AF-BE57-76B52DF47F52@FreeBSD.org> <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29.05.2013 11:06, Warner Losh wrote: > On May 29, 2013, at 2:47 AM, David Chisnall wrote: > >> On 29 May 2013, at 07:57, Andriy Gapon <avg@FreeBSD.org> wrote: >> >>> In fact, I am of opinion that while such bugs exist gcc should be crowned back >>> as a default compiler. >> Seriously? Your show stopper bug is that, very occasionally, clang emits incorrect debug info? And Steve's is that clang emits code that is fully compliant with the C standard, but gives more floating point precision than he wanted? >> >> If those are the most serious problems we have with clang, then it's time to remove gcc 4.2.1 from the tree right now. I wish the problems that we had with it were so trivial... > NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO > ... > There are serious problems with clang on arm right now. And it doesn't support mips. Removing gcc is way premature. > > Warner > I didn't meant to start a clang vs gcc thread but it's evident that we were actually in need of expressing the issues about clang and the future of the tool chain. IMHO: - gcc has to go. It is old and, despite the scotch tape, unmaintained. libstdc++ in particular really has to go first: it is too confusing to have two C++ libraries where one of them is simply obsolete. OpenOffice, for example was recently ported to clang and libc++ however it will not work with the libstdc++ in base due to lack of C++11 support. - clang is not ready but it is getting there: I appreciate greatly having compiler_rt and the new C++ stack available. Unfortunately I do agree with the opinion that clang is taking too long to build and has become a bottleneck for buildworld. Now I would really like to see both gcc and clang living as packages outside of base. This would also mean that the installer has to start learning about pkgng (which is one of the things I miss about sysinstall). It's all wishful thinking though so I just want to thank everyone that is doing the real work both making an external toolchain possible and improving clang support. Regards, Pedro.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51A77A22.3040103>