From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16510 invoked by alias); 14 Dec 2015 14:40:22 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 16494 invoked by uid 89); 14 Dec 2015 14:40:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pf0-f172.google.com Received: from mail-pf0-f172.google.com (HELO mail-pf0-f172.google.com) (209.85.192.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 14 Dec 2015 14:40:14 +0000 Received: by pfbo64 with SMTP id o64so27724750pfb.1 for ; Mon, 14 Dec 2015 06:40:13 -0800 (PST) X-Received: by 10.98.13.22 with SMTP id v22mr35996752pfi.125.1450104012924; Mon, 14 Dec 2015 06:40:12 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id 79sm42978777pfb.67.2015.12.14.06.40.09 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 14 Dec 2015 06:40:12 -0800 (PST) From: Yao Qi To: Pedro Alves Cc: "gdb\@sourceware.org" Subject: Re: C++ conversion status update References: <565460FB.6070103@redhat.com> Date: Mon, 14 Dec 2015 14:40:00 -0000 In-Reply-To: <565460FB.6070103@redhat.com> (Pedro Alves's message of "Tue, 24 Nov 2015 13:07:07 +0000") Message-ID: <86zixdnlfg.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00011.txt.bz2 Pedro Alves writes: > Good news, we've reached a significant milestone on the C++ conversion --= on > a few important hosts, GDB now builds cleanly as a C++ program with no > hacks. These are at least: > > - Aarch64 GNU/Linux > - ARM GNU/Linux > - x86 GNU/Linux > - x86_64 GNU/Linux > - x86_64 Mingw-w64 > > In addition, the testsuite shows no regressions in C++ mode, compared to = C mode. > We need a wiki page to track these hosts on which we enabled C++ build. Like this gcc wiki page, https://gcc.gnu.org/wiki/CppBuildStatus or we can track them in existing https://sourceware.org/gdb/wiki/cxx-conversion wiki page. > The plan I propose next is to default to building in C++ mode on hosts > that are known to build cleanly in C++ mode. Or rather, change the defau= lt > to be C++ mode, _except_ for hosts/ports that haven't been converted > yet. I prefer the latter. > Then, as ports get converted, one by one they'll be removed from > the "can't do C++ yet" list. That gives us a defined stopping point -- w= hen > the list becomes empty, and after a reasonable period, we can decide to r= emove > support for building in C mode and start making use of C++ features. That sounds good to me. > > The question I have is which hosts (Architecture + OS combination) people > care about that still need C++ conversion work and thus should be on > that list? How about all linux and mingw hosts? assuming that xtensa can be converted. > > This is where anyone can help! > > I've created the "users/palves/cxx-conversion" branch (on sourceware.org) > where I committed a patch that implements the list idea. I filled in > a set of hosts that I _thought_ wouldn't build, but I don't really know > for sure. > > So I'd like to invite people to try to build master on their favorite > host with --enable-build-with-cxx, and report back the result. We didn't hear anything on this yet, but we can't wait for it forever. I'd like to turn on C++ build for linux and mingw hosts in default after the 7.11 release branch is created. --=20 Yao (=E9=BD=90=E5=B0=A7)