Re: C++ conversion status update

Pedro Alves
2016-04-13T14:04:05Z

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