Re: [PATCH 0/6] [C++] Drop -fpermissive hack, enable -Werror

[Yao Qi <qiyaoltc@gmail.com>]

Pedro Alves <palves@redhat.com> 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 clear).
> 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.
>  
>  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?

-- 
Yao (齐尧)