Date: Thu, 17 Mar 2011 16:07:14 +0300 From: Konstantin Tokarev <annulen@yandex.ru> To: Alberto Villa <avilla@freebsd.org> Cc: Doug Barton <dougb@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Compiling ports in a post-9.0-RELEASE world Message-ID: <123121300367234@web45.yandex.ru> In-Reply-To: <105381300365591@web53.yandex.ru> References: <4D7BED01.6000506@FreeBSD.org> <201103160028.01687.avilla@freebsd.org> <241821300263308@web137.yandex.ru> <201103160933.48175.avilla@freebsd.org> <105381300365591@web53.yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
17.03.2011, 15:39, "Konstantin Tokarev" <annulen@yandex.ru>: > 16.03.2011, 11:33, "Alberto Villa" <avilla@freebsd.org>;: > >> šOn Wednesday 16 March 2011 09:15:07 Konstantin Tokarev wrote: >>> ššFrom http://clang.llvm.org/docs/LanguageExtensions.html >>> >>> šš"In addition to the language extensions listed here, Clang aims to >> šsupport >>> šša broad range of GCC extensions." >>> >>> ššSo GCC extensions may also be considered as missing features. >> šgcc-isms also means "bad code which is nonetheless supported by gcc" > > In this case don't hesitate to file a bug against gcc :) Let me elaborate my idea a bit. One may think that reporting bugs on GCC he supports development of technology that FreeBSD does not endorse [1]. I don't think so. 1) Latest versions of GCC are more standard-compliant than earlier ones, and bad written code tends to produce compilation errors with newer GCC. For example, I've seen lots of legacy code written for GCC 3.x but failing to compile with 4.x. 4.x branch is also being improved. 2) Active upstreams and Linux distributions try to make code compatible with latest and greatest GCC. So if newer version is fixed not to compile some kind of broken code, there will be big chances that upstreams will fix it themselves. 3) Projects with dead upstreams should be excluded from ports collection someday, unless maintainers are willing to do "upstream" job. Folks using this software will be able to build it using "right" GCC version which is known to compile this "crap" properly. And last but not least, GCC is still great compiler, despite of its drawbacks and licensing issues. [1] Bugs could be reported only for latest GCC version, i.e. 4.5.2, and 4.2.x will never get fixes. -- Regards, Konstantin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?123121300367234>