From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65646 invoked by alias); 13 Apr 2016 14:04:05 -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 65552 invoked by uid 89); 13 Apr 2016 14:04:05 -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=excuse, sk:confirm, 8.0, crossed 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 14:03:58 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (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 54E587822E; Wed, 13 Apr 2016 14:03:57 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u3DE3t8k030847; Wed, 13 Apr 2016 10:03:56 -0400 Subject: Re: C++ conversion status update To: Joel Brobecker References: <565460FB.6070103@redhat.com> <86zixdnlfg.fsf@gmail.com> <566F13D4.9000900@redhat.com> <570D91F6.2020702@redhat.com> <20160413124127.GG31406@adacore.com> Cc: Yao Qi , "gdb@sourceware.org" From: Pedro Alves Message-ID: <570E51CB.6010304@redhat.com> Date: Wed, 13 Apr 2016 14:04: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: <20160413124127.GG31406@adacore.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-04/txt/msg00009.txt.bz2 On 04/13/2016 01:41 PM, Joel Brobecker wrote: >> 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? > > I wish I could say I'm ready for the switch, but I'm not. Mostly, > it's cross-compiling gdbserver, because I need to start building > a C++ cross-compiler to be able to achieve that. But I don't think > I can use that excuse to hold you guys back forever. If others > are in the same situation, then we might have to reconsider our > timeline, but so far as I know, I'm the only one. So, I'm OK with > changing the default as well. OK. We can just add an entry to lynxos to GDB_AC_BUILD_WITH_CXX to make it default to C, still. Like this, against the version in the users/palves/cxx-conversion branch: diff --git i/gdb/build-with-cxx.m4 w/gdb/build-with-cxx.m4 index aa3661f..e42719e 100644 --- i/gdb/build-with-cxx.m4 +++ w/gdb/build-with-cxx.m4 @@ -30,6 +30,7 @@ AC_DEFUN([GDB_AC_BUILD_WITH_CXX], *-*nto* | \ *-*bsd* | \ xtensa*-*-linux* | \ + *-*-lynxos* | \ null) enable_build_with_cxx=no ;; *) That'll give you until all the other hosts are confirmed-converted, at least. > > If we do, perhaps it's time to change the major version number > to 8.0? > Or maybe defer that until we actually declare C mode unsupported. I myself hope to do that before the next release, but ... :-) (Another thought that crossed my mind before is to switch the numbering scheme to follow something like gcc's. That is, make the minor number be the major number going forward, as the minor number actually counts new-feature releases, while the major number is arbitrary.) Thanks, Pedro Alves