From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: C++ conversion status update
Date: Wed, 13 Apr 2016 00:25:00 -0000 [thread overview]
Message-ID: <570D91F6.2020702@redhat.com> (raw)
In-Reply-To: <566F13D4.9000900@redhat.com>
On 12/14/2015 07:09 PM, Pedro Alves wrote:
> On 12/14/2015 02:40 PM, Yao Qi wrote:
>> Pedro Alves <palves@redhat.com> writes:
>
>
>> 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.
>
> Ok.
>
>>
>>> 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.
>
> Ok, that's my preference as well.
>
>>
>>>
>>> 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.
>
> x86-64 and x86 mingw built cleanly last I tried.
>
> I don't know about _all_ Linux hosts, hence the RFH.
>
> At least x86, x86_64, Aarch64, ARM, and PPC64 build cleanly. Or did, a
> few weeks back.
>
>>>
>>> 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.
>
> Yeah. I got enthusiastic support offlist for C++ in general, but people
> don't seem to really be that interested or paying attention to random
> host architectures.
>
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?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-04-13 0:25 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 [this message]
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=570D91F6.2020702@redhat.com \
--to=palves@redhat.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