From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59085 invoked by alias); 20 Nov 2015 09:46:14 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 59072 invoked by uid 89); 20 Nov 2015 09:46:13 -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-pa0-f43.google.com Received: from mail-pa0-f43.google.com (HELO mail-pa0-f43.google.com) (209.85.220.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 20 Nov 2015 09:46:12 +0000 Received: by padhx2 with SMTP id hx2so111979675pad.1 for ; Fri, 20 Nov 2015 01:46:10 -0800 (PST) X-Received: by 10.66.158.169 with SMTP id wv9mr1430459pab.138.1448012769423; Fri, 20 Nov 2015 01:46:09 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id sx1sm5986971pbc.36.2015.11.20.01.46.06 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 20 Nov 2015 01:46:08 -0800 (PST) From: Yao Qi To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org, Simon Marchi Subject: Re: [PATCH 0/6] [C++] Drop -fpermissive hack, enable -Werror References: <1447864802-24016-1-git-send-email-palves@redhat.com> <564CB8EC.5000203@gmail.com> <564CBB15.7020209@redhat.com> <867fle1b5z.fsf@gmail.com> <564DE744.8030104@redhat.com> Date: Fri, 20 Nov 2015 09:46:00 -0000 In-Reply-To: <564DE744.8030104@redhat.com> (Pedro Alves's message of "Thu, 19 Nov 2015 15:14:12 +0000") Message-ID: <86lh9types.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-11/txt/msg00415.txt.bz2 Pedro Alves writes: > Yeah, my plan here was to "lock" (*) ports to C++ mode one by one, as soon > as they build in C++ mode. Actually, I think a negative/reverse list is = even > better. This allows keeping track of ports/hosts people really still care > about, and, gives us an easy defined stopping point (when the list is cle= ar). > What would you think of this approach? Yes, this approach is OK to me. However, as you said, we need to announce this on gdb@ first. Before we build GDB in C++ mode for some hosts, we need to test it. IIRC, we didn't test GDB built in C++ before. Another thing in my mind is the release schedule. We have two months, but people are off around Christmas and New Year. Do we want GDB 8.0 built in C++ in default in some hosts, such as linux? I am not sure. > > I should probably move this to a separate thread, push this to a branch on > sourceware.org (to collect a better initial set of still-needs-conversion= -work > hosts, with community help) and announce the intent on the gdb@ list, for > wider visibility/discussion. Yes, let's do that. > --- > gdb/build-with-cxx.m4 | 18 ++++++++++++++++-- > gdb/configure | 17 +++++++++++++++-- > gdb/gdbserver/configure | 17 +++++++++++++++-- > 3 files changed, 46 insertions(+), 6 deletions(-) > > diff --git a/gdb/build-with-cxx.m4 b/gdb/build-with-cxx.m4 > index b6284fd..03ff54d 100644 > --- a/gdb/build-with-cxx.m4 > +++ b/gdb/build-with-cxx.m4 > @@ -21,6 +21,21 @@ dnl allowing a user to build with a C++ compiler. >=20=20 > AC_DEFUN([GDB_AC_BUILD_WITH_CXX], > [ > + # The "doesn't support C++ yet" hall of shame. > + case $host in > + *-*aix* | \ > + *-*go32* | \ > + *-*darwin* | \ > + *-*solaris* | \ > + *-*nto* | \ > + *-*bsd* | \ > + xtensa*-*-linux* | \ Why do we especially exclude xtensa*-*-linux* from building in C++ mode? --=20 Yao (=E9=BD=90=E5=B0=A7)