From: Dmitry Samersoff <dms@samersoff.net>
To: Pedro Alves <palves@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Go C++ only
Date: Thu, 01 Sep 2016 17:48:00 -0000 [thread overview]
Message-ID: <5cc4dfad-ff68-333b-4575-9e824582da68@samersoff.net> (raw)
In-Reply-To: <212bc30a-e6ad-886b-0881-8206dd91b933@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 906 bytes --]
Pedro,
I'm not a gdb developer but I'm *for* this changes.
+1
-Dmitry
On 2016-09-01 20:32, Pedro Alves wrote:
> Hi all,
>
> As last discussed, the general consensus was to make 7.12
> the last gdb version that supports building with a C compiler.
>
> I've been holding proposing to drop C-mode support in master
> with the idea that that would help with all the bugfix
> backporting going on. I've had to explain this several times
> recently, as people are eager to use C++ features. Multiple
> times this week, even.
>
> At this point the backporting rate is quite low though, so
> maybe it no longer makes that much sense to hold C++ back,
> at least in new code.
>
> What do people think? Time to march ahead?
>
> Thanks,
> Pedro Alves
>
--
Dmitry Samersoff
Saint Petersburg, Russia, http://devnull.samersoff.net
* There will come soft rains ...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-01 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 17:32 Pedro Alves
2016-09-01 17:48 ` Dmitry Samersoff [this message]
2016-09-01 18:07 ` Simon Marchi
2016-09-01 18:22 ` Pedro Alves
2016-09-01 18:33 ` Simon Marchi
2016-09-01 18:48 ` Pedro Alves
2016-09-01 18:56 ` Pedro Alves
2016-09-01 18:36 ` Andrew Pinski
2016-09-01 19:01 ` Eli Zaretskii
2016-09-01 19:07 ` Pedro Alves
2016-09-01 18:17 ` Joel Brobecker
2016-09-02 10:01 ` Yao Qi
2016-09-02 10:15 ` Pedro Alves
2016-09-02 15:34 ` Sergio Durigan Junior
2016-09-02 20:10 ` Sergio Durigan Junior
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=5cc4dfad-ff68-333b-4575-9e824582da68@samersoff.net \
--to=dms@samersoff.net \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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