From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 53172 invoked by alias); 13 Apr 2016 00:25:40 -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 53160 invoked by uid 89); 13 Apr 2016 00:25:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=invite, paying, favorite, hear X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 13 Apr 2016 00:25:29 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 100AB20A89; Wed, 13 Apr 2016 00:25:28 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u3D0PQ1j012503; Tue, 12 Apr 2016 20:25:27 -0400 Subject: Re: C++ conversion status update To: Yao Qi References: <565460FB.6070103@redhat.com> <86zixdnlfg.fsf@gmail.com> <566F13D4.9000900@redhat.com> Cc: "gdb@sourceware.org" From: Pedro Alves Message-ID: <570D91F6.2020702@redhat.com> Date: Wed, 13 Apr 2016 00:25:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <566F13D4.9000900@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-04/txt/msg00006.txt.bz2 On 12/14/2015 07:09 PM, Pedro Alves wrote: > On 12/14/2015 02:40 PM, Yao Qi wrote: >> Pedro Alves writes: > > >> 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. > > Ok. > >> >>> 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 default >>> 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 -- when >>> the list becomes empty, and after a reasonable period, we can decide to remove >>> support for building in C mode and start making use of C++ features. >> >> That sounds good to me. > > Ok, that's my preference as well. > >> >>> >>> 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. > > x86-64 and x86 mingw built cleanly last I tried. > > I don't know about _all_ Linux hosts, hence the RFH. > > At least x86, x86_64, Aarch64, ARM, and PPC64 build cleanly. Or did, a > few weeks back. > >>> >>> 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. > > Yeah. I got enthusiastic support offlist for C++ in general, but people > don't seem to really be that interested or paying attention to random > host architectures. > Now that the "exceptions signals handlers" issue is resolved, I think we've now done all we could re. C++ conversion while keeping C supported as well. I think the time has come to starting to default to building in C++ mode on all hosts, except those known to not having been fully converted yet, as with the patch at the top of the users/palves/cxx-conversion branch. Thoughts? Thanks, Pedro Alves