From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: C++ conversion status update
Date: Mon, 14 Dec 2015 14:40:00 -0000 [thread overview]
Message-ID: <86zixdnlfg.fsf@gmail.com> (raw)
In-Reply-To: <565460FB.6070103@redhat.com> (Pedro Alves's message of "Tue, 24 Nov 2015 13:07:07 +0000")
Pedro Alves <palves@redhat.com> writes:
> Good news, we've reached a significant milestone on the C++ conversion -- on
> a few important hosts, GDB now builds cleanly as a C++ program with no
> hacks. These are at least:
>
> - Aarch64 GNU/Linux
> - ARM GNU/Linux
> - x86 GNU/Linux
> - x86_64 GNU/Linux
> - x86_64 Mingw-w64
>
> In addition, the testsuite shows no regressions in C++ mode, compared to C mode.
>
We need a wiki page to track these hosts on which we enabled C++ build.
Like this gcc wiki page, https://gcc.gnu.org/wiki/CppBuildStatus or we
can track them in existing https://sourceware.org/gdb/wiki/cxx-conversion
wiki page.
> The plan I propose next is to default to building in C++ mode on hosts
> that are known to build cleanly in C++ mode. Or rather, change the default
> to be C++ mode, _except_ for hosts/ports that haven't been converted
> yet.
I prefer the latter.
> Then, as ports get converted, one by one they'll be removed from
> the "can't do C++ yet" list. That gives us a defined stopping point -- when
> the list becomes empty, and after a reasonable period, we can decide to remove
> support for building in C mode and start making use of C++ features.
That sounds good to me.
>
> The question I have is which hosts (Architecture + OS combination) people
> care about that still need C++ conversion work and thus should be on
> that list?
How about all linux and mingw hosts? assuming that xtensa can be
converted.
>
> This is where anyone can help!
>
> I've created the "users/palves/cxx-conversion" branch (on sourceware.org)
> where I committed a patch that implements the list idea. I filled in
> a set of hosts that I _thought_ wouldn't build, but I don't really know
> for sure.
>
> So I'd like to invite people to try to build master on their favorite
> host with --enable-build-with-cxx, and report back the result.
We didn't hear anything on this yet, but we can't wait for it forever.
I'd like to turn on C++ build for linux and mingw hosts in default after
the 7.11 release branch is created.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-12-14 14:40 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 [this message]
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
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=86zixdnlfg.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--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