From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84583 invoked by alias); 13 Apr 2016 14:40:24 -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 84561 invoked by uid 89); 13 Apr 2016 14:40:23 -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=grace, 80 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:40:22 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (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 4CD9A627E0; Wed, 13 Apr 2016 14:40:21 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u3DEeJwK017304; Wed, 13 Apr 2016 10:40:20 -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> <570E51CB.6010304@redhat.com> <20160413141648.GI31406@adacore.com> Cc: Yao Qi , "gdb@sourceware.org" From: Pedro Alves Message-ID: <570E5A53.8070306@redhat.com> Date: Wed, 13 Apr 2016 14:40: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: <20160413141648.GI31406@adacore.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-04/txt/msg00015.txt.bz2 On 04/13/2016 03:16 PM, Joel Brobecker wrote: >> 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. > > We could do that indeed; or, IIRC, there is a configure option > to force the use of C instead of C++. It's --enable-build-with-cxx=yes|no. That hunk above decides the default for when the --enable-build-with-cxx option is not specified. I don't mind requiring > the user to force it; it's a good reminder (and ties in nicely > with another comment below). Hmm. That's an excellent point. If others are OK with it, I'm in favor too. >>> 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 ... :-) > > :-). I know it sounds self-serving, but I think we should be giving > users a one-release grace period. Make C++ the default, but with > C support for those who can't build with C++. That way, they can > still build, but they are clearly on notice about the impending > change. Then, as soon as the release branch is cut, we can flip > the switch. That way, I don't think you'll have to keep the compat > mode for much longer than you were planning to. That may well be. Thanks, Pedro Alves