From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 497 invoked by alias); 6 Jun 2012 22:59:05 -0000 Received: (qmail 485 invoked by uid 22791); 6 Jun 2012 22:59:03 -0000 X-SWARE-Spam-Status: No, hits=-7.8 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,TW_CX X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Jun 2012 22:58:49 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1ScPBf-0002Wo-GL from Thomas_Schwinge@mentor.com ; Wed, 06 Jun 2012 15:58:47 -0700 Received: from feldtkeller.schwinge.homeip.net ([172.30.72.195]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2012 23:58:45 +0100 From: Thomas Schwinge To: Diego Novillo Cc: gcc Subject: Re: RFH - Testing targets for the switch to C++ In-Reply-To: References: User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu) Date: Wed, 06 Jun 2012 22:59:00 -0000 Message-ID: <87r4tskpya.fsf@schwinge.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2012-06/txt/msg00107.txt.bz2 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-length: 1597 Hi! A bit late to the game... :-) On Fri, 6 Apr 2012 18:55:28 -0400, Diego Novillo wrot= e: > I have started testing the switch to C++ and there is a pile of > testing to be done. The testing itself is trivial, but the number of > targets that need to be tested is large and I don't have access to all > these combinations. i686-gnu would be mine. This is based on 8b64dc3c58b54d07156c99a24576be76e8cbdc10 (2012-05-28) sources, doing native builds on x86 Debian GNU/Linux as well as x86 Debian GNU/Hurd. When --enable-build-with-cxx is enabled: * Build time mostly stays the same. * Looking at the build log, the build system's gcc (as opposed to g++) is still being used for building libiberty, fixincludes, zlib, libdecnumber, *_FOR_BUILD stuff in gcc/Makefile. The latter seems to have been addressed in a44c8c3b1ee8ae1779fd8ee1ad556ed86a608bd2 (2012-05-31), the others are probably expected to continue using gcc. * The size of the build directory stage1-gcc shrinks (!) from 1.1 GiB to 0.4 GiB, such that the whole build tree then occupies 2.6 GiB instead of 3.2 GiB. I did notice that the C build uses -fkeep-inline-functions, and the C++ build doesn't (my logs, and confirmed in the top-level configure.ac), but don't know if that is the (sole) reason; I have not looked at this in more detail -- but 0.6 GiB or 60 % less is quite a bit. * No difference in testsuite results. When building a i686-linux-gnu to i686-gnu cross-compiler, there are (expectedly) no surprises either. Gr=C3=BC=C3=9Fe, Thomas --=-=-= Content-Type: application/pgp-signature Content-length: 489 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJPz+CdAAoJENuKOtuXzphJJawH/iylq6NSqC0/C+Z+l9tTqRLV ZuPO5EuF2KDyaNCYRZ+9meLpnyVPy3k/DCBZ7yom3eR1HPfFOjc+3T94OPPFIbgC Cx6ay35Od3h3KPr7bI6E5wQoyW5neljz6tEo5qrx+rGUQrDqRH5ng881usYJR84P /HRozgMatIUT+QKS5Xk9H/HgVV9XXnXhcswK2VSaqMRCqKoNBsvZlmMcRfUy14mB T9neYi2E3J1hW5mFxkrVeG8IXF9tqyF9UHW0XW2jYyh18oiwBWKe9qlV/NhYQxsM 2EemmIHWkXgZwQzXm2Dft/jAUPDFJ/8sLdQd3iP1Cj10hdShHICuwe0SZlR7vqI= =5kUU -----END PGP SIGNATURE----- --=-=-=--