Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/1] Build GDB as a C++ program by default
Date: Tue, 19 Apr 2016 13:34:00 -0000	[thread overview]
Message-ID: <571633C8.4060803@ericsson.com> (raw)
In-Reply-To: <1461000466-31668-1-git-send-email-palves@redhat.com>

On 16-04-18 01:27 PM, Pedro Alves wrote:
> It's been a long ride, but GDB now builds cleanly as a C++ program on
> most supported systems.
> 
> There are a few host-specific files that may be missing the occasional
> cast, but for all I know, most of the codebase has been converted and
> builds cleanly, with no undefined behavior and no hacks.
> 
> It's time to try building GDB with a C++ compiler by default, which is
> what the the following trivial patch does.
> 
> Following the discussion on the gdb@ list, this flips the default on
> all hosts, unconditionally.
> 
> Note that it's still possible to revert back to building with a C
> compiler, by configuring with --enable-build-with-cxx=no.  For the
> moment, we have a Fedora buildslave specifically set up to catch
> C-mode build failures on Fedora, so C-mode breakage should still be
> noticed and fixed promptly.
> 
> The decision of when to drop C-mode support will be done at some other
> moment, possibly only after the next release.
> 
> Pedro Alves (1):
>   Build GDB as a C++ program by default
> 
>  gdb/build-with-cxx.m4   | 2 +-
>  gdb/configure           | 2 +-
>  gdb/gdbserver/configure | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 

Does that mean that all supported hosts have been tested to build in C++?


  parent reply	other threads:[~2016-04-19 13:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 17:27 Pedro Alves
2016-04-18 17:27 ` [PATCH 1/1] " Pedro Alves
2016-04-19  7:34   ` Yao Qi
2016-04-19 13:34 ` Simon Marchi [this message]
2016-04-19 14:18   ` [PATCH 0/1] " Pedro Alves
2016-04-19 14:48     ` Eli Zaretskii
2016-04-19 15:03       ` Pedro Alves
2016-04-19 15:23         ` Eli Zaretskii
2016-04-19 15:40           ` Pedro Alves
2016-04-19 15:59             ` Eli Zaretskii
2016-04-19 16:20               ` Pedro Alves
2016-04-19 16:31               ` Eli Zaretskii
2016-04-19 15:41       ` Simon Marchi
2016-04-19 16:32         ` Eli Zaretskii
     [not found]     ` <AC542571535E904D8E8ADAE745D60B19445B1C11@IRSMSX104.ger.corp.intel.com>
     [not found]       ` <5716425B.3050707@intel.com>
     [not found]         ` <57164325.8020408@redhat.com>
2016-04-19 15:20           ` Walfred Tedeschi
2016-04-20 19:56             ` Pedro Alves
2016-04-20 22:16               ` Pedro Alves
2016-04-21 15:18               ` John Baldwin
2016-04-21 16:41                 ` Pedro Alves
2016-04-19 15:47     ` Simon Marchi
2016-04-19 15:50       ` Pedro Alves
2016-04-20 22:27     ` 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=571633C8.4060803@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@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