Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: C++ conversion status update
Date: Wed, 13 Apr 2016 14:04:00 -0000	[thread overview]
Message-ID: <570E51CB.6010304@redhat.com> (raw)
In-Reply-To: <20160413124127.GG31406@adacore.com>

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


  reply	other threads:[~2016-04-13 14:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 13:07 Pedro Alves
2015-12-14 14:40 ` Yao Qi
2015-12-14 19:09   ` Pedro Alves
2015-12-15 11:39     ` Jose E. Marchesi
2015-12-15 20:03       ` Simon Marchi
2015-12-16  0:19         ` Pedro Alves
2015-12-16  0:21           ` Pedro Alves
2015-12-16  1:19             ` Simon Marchi
2015-12-16 20:11               ` Pedro Alves
2015-12-16 20:15       ` Pedro Alves
2015-12-16 20:30         ` Simon Marchi
2015-12-16 22:10           ` Pedro Alves
2015-12-16 22:59             ` Pedro Alves
2016-01-19 19:00     ` John Baldwin
2016-01-20 11:10       ` Pedro Alves
2016-01-20 23:33         ` John Baldwin
2016-01-21 11:38           ` Pedro Alves
2016-04-16  0:21           ` Pedro Alves
2016-04-18 16:51             ` Pedro Alves
2016-04-19 19:26               ` John Baldwin
2016-04-19 20:36                 ` Pedro Alves
2016-04-19 21:40                   ` John Baldwin
2016-04-19 22:20                     ` Pedro Alves
2016-04-13  0:25     ` Pedro Alves
2016-04-13 11:07       ` Yao Qi
2016-04-13 14:13         ` Pedro Alves
2016-04-13 14:31           ` Sergio Durigan Junior
2016-04-13 12:41       ` Joel Brobecker
2016-04-13 14:04         ` Pedro Alves [this message]
2016-04-13 14:16           ` Joel Brobecker
2016-04-13 14:27             ` Luis Machado
2016-04-13 14:35             ` Marc Khouzam
2016-04-13 14:59               ` Joel Brobecker
2016-04-13 14:40             ` Pedro Alves
2016-04-18 17:29               ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=570E51CB.6010304@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox