From owner-freebsd-current@FreeBSD.ORG Thu May 2 18:08:40 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68BC4FCC; Thu, 2 May 2013 18:08:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 58FA61DE6; Thu, 2 May 2013 18:08:39 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r42I8ZW7070828; Thu, 2 May 2013 21:08:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.2 kib.kiev.ua r42I8ZW7070828 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r42I8Z29070827; Thu, 2 May 2013 21:08:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 2 May 2013 21:08:35 +0300 From: Konstantin Belousov To: Davide Italiano Subject: Re: Kernel build error in hwpmc with system GNU cc Message-ID: <20130502180834.GL3047@kib.kiev.ua> References: <51820AFD.1030607@freebsd.org> <51826D52.6030403@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vH3HHxf962mwD/qo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 May 2013 18:08:40 -0000 --vH3HHxf962mwD/qo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 02, 2013 at 04:12:36PM +0200, Davide Italiano wrote: > On Thu, May 2, 2013 at 3:42 PM, Andrey Chernov wrote: > > On 02.05.2013 14:06, Davide Italiano wrote: > >>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning= : 'map' may be used uninitialized in this function > >>> *** [hwpmc_core.o] Error code 1 > > > >> You can find a patch attached at the end of this mail that should fix > >> the problem. > > > > Thanks, it fix this warning. > > > >> More generally speaking, why are you building -CURRENT using GCC while > >> the default compiler has been clang since November 2012? > > > > 1) clang is not ready for production, it is too buggy. See its fixes > > rate for very common things 'must work' in every compiler. It is > > included into -current not because of its quality, but to involve > > developers into clang bugfixes to make its progress faster, and > > personally me don't want to find clang bugs. > > > > 2) Its build time is too long. > > > > 3) It generates bigger code. > > > >> Putting the additional burden of > >> testing on the committer because two compilers are supported at the > >> same time doesn't scale really well, at least according to me. > > > > You'll hit this error later in any case, attempting to MFC your changes > > to -stable with GNU cc. > > > > -- > > bitcoin:13fGiNutKNHcVSsgtGQ7bQ5kgUKgEQHn7N >=20 >=20 > I won't object about your 2) and 3), but if you fear to hit bugs you > shouldn't probably run -CURRENT. > About the backport, I faced the problem of adapting code in the past > when merging to stable releases, so this is actually a different > problem. If I'd blindly merged the incrimined change to 9-STABLE > without building and notifying the GCC warning, then I would expect > you ranting at me because of build failure. > There's a notion of "default compiler" in 9 and in 10 and they're > different. My opinion is that people should live with it, and unless > someone will introduce some mechanism a-la redports.org to overcome > the issue, I will take my risks committing changes and fixing failures > if they occur. It's already really difficult to have tinderbox not > ranting these days, adding another compiler just result in another > dimension of complexity in the whole scenario. I experienced the same issues e.g. with the TTM commit, on somewhat bigger scale. There were 3 or 4 problems compiling the code with gcc, which were silently accepted by clang. Most ridiculous was clang silence on the double-declaration of the functions. For myself, I decided after the episode that I am morally unblended if default build is fine after the commit. For any compile issues reported by users with non-default compilers, I obviously take a look and do fix if possible, but I certainly do not intend to even try to test with non-default compiler on my own. --vH3HHxf962mwD/qo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRgquiAAoJEJDCuSvBvK1B0csP/06PV83F4/mTZJF2qMXV/FhQ /JzpyXn3VlBm1OndN0CwWb03wPhOrIccpAPK/nl+b3YYHN/XuOmY2knd6wA0mxky D5gFL9IRzSLbh+9nUlTyiEs1O+xySFxXjhmLSa6Xu55NVkAKFl5NX7XqQm6cQSlQ DZbxzUV8MaUm/r390jm3pN8k/feB5zzjoJOfBafU71OU7mRrdhlMlAcQ0+6igqcE t2yE/ID/YQqhUwbyFsEJRbmg1ff0CMSNpUBgZdGmNkPnTU7+3dTSoqyGdFZUTbCn kN+yyqfVg0HuyUZXSA+E5Qiin4PAxK+zfsTNR1r9jCaDGszejQFK9F6IbksOx63P 7lU02lNE2dcTlzF6N03nXRebUTZmxvFFYzW7KDNHU2EIAG73huGFjr3SiUYYyp8z OpviUcI7WxSmfGLe3iC/5qnbBM8QAT/0HGzcrZlHGe3b9LjIdmtUKAyinhVjBuzG CEQsRf+bL03gNlJJAi2eUBl7olxHU6fB2wSgmeaDioKE4oeGELPnFSIbllo60cIY Gm9s0PMiG8/YXEs1vVYiMi/CVy6QSzxmKqyHJJwNUetc4iyLKZ5FHWPZIeaWIrDI 1AJaFGoraH3tfL65r3bosgbs8Abmy6/uuTw6/K++0U6h13VD61C1aI1KaGhiWTl6 PFX5Tl0grztGY5qYXDqX =DnJH -----END PGP SIGNATURE----- --vH3HHxf962mwD/qo--