From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128527 invoked by alias); 13 Apr 2016 14:27:15 -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 128500 invoked by uid 89); 13 Apr 2016 14:27:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=grace, impending, nicely, 80 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 13 Apr 2016 14:27:13 +0000 Received: from svr-orw-fem-05.mgc.mentorg.com ([147.34.97.43]) by relay1.mentorg.com with esmtp id 1aqLl8-0006W8-KY from Luis_Gustavo@mentor.com ; Wed, 13 Apr 2016 07:27:10 -0700 Received: from [172.30.4.91] (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.3.224.2; Wed, 13 Apr 2016 07:27:10 -0700 Subject: Re: C++ conversion status update 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> To: Joel Brobecker , Pedro Alves CC: Yao Qi , "gdb@sourceware.org" Reply-To: Luis Machado From: Luis Machado Message-ID: <570E573C.4010802@codesourcery.com> Date: Wed, 13 Apr 2016 14:27:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160413141648.GI31406@adacore.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00012.txt.bz2 On 04/13/2016 09:16 AM, 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++. I don't mind requiring > the user to force it; it's a good reminder (and ties in nicely > with another comment below). > >>> 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. I like the idea of the one-release grace period. We've been discussing this for years anyway, waiting 6 additional months does not sound so bad. :-) That gives toolchains enough time to adapt. So we're probably talking GDB 7.13 built with a C++ compiler?