public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: C++ draft
Date: Tue, 28 Jun 2011 04:33:00 -0000	[thread overview]
Message-ID: <BANLkTikaPrf26ZhAn05qHUM8qnGXus9tOg@mail.gmail.com> (raw)
In-Reply-To: <m3tybb7zjz.fsf@fleche.redhat.com>

On Mon, Jun 27, 2011 at 2:08 PM, Tom Tromey <tromey@redhat.com> wrote:

> 1. Modify GDB so it can be compiled with -Wc++-compat.
>   This would be the first patch series.  There is already an archer
>   branch for this.

fwiw, -Wc++-compat was complete, but requires merging to head
(about 4 months old), latest push is about 9 months old..
don't imagine it'll take me too long to do that merge.
knock on wood.

> 2. Then, change GDB to compile with a C++ compiler (-Wc++-compat is
>   not complete).  This would be the second patch series.

I had started on this locally, but did not get very far into it.
the patches here are a little less mechanical than -Wc++-compat.
i'll try and muster up some motivation to work on these 2 things.

  parent reply	other threads:[~2011-06-28  4:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 21:08 Tom Tromey
2011-06-27 21:23 ` [Archer] " Joel Brobecker
2011-06-29 19:55   ` Tom Tromey
2011-06-29 21:47     ` [Archer] " Joel Brobecker
2011-06-28  4:33 ` Matt Rice [this message]
2011-06-28  8:21 ` Yao Qi
2011-06-28 12:21   ` Gary Benson
2011-06-28 17:08     ` Matt Rice
2011-06-28 17:36     ` Jan Kratochvil
2011-06-29 20:08     ` Tom Tromey
2011-06-29 20:06   ` Tom Tromey
2011-06-30  6:06     ` Yao Qi
2011-09-26 21:01       ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs
2011-06-29 19:03   ` [Archer] " Joel Brobecker

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=BANLkTikaPrf26ZhAn05qHUM8qnGXus9tOg@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=archer@sourceware.org \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).