Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/8] Add Rust language support
Date: Wed, 27 Apr 2016 11:47:00 -0000	[thread overview]
Message-ID: <5720A6B6.8010505@redhat.com> (raw)
In-Reply-To: <1461725371-17620-1-git-send-email-tom@tromey.com>

On 04/27/2016 03:49 AM, Tom Tromey wrote:
> Hi.  It's been a while.

Hi.  Great to see you around.

> This patch series adds support for the Rust programming languages to
> gdb.  See https://www.rust-lang.org/ for more information on Rust
> itself.
> 
> This is a reasonably full-featured port.  It has a few known bugs and
> holes, but nothing very serious.

This is awesome!

I've read the series and it looks mostly OK to me.  Just a few minor
nits here and there.

> I've tested it using Rust 1.8, as available in the Fedora COPR.  It's
> known not to work with Rust nightly, due to some debuginfo regressions
> there.
> 
> I ran the new tests with gcov.  The test cases cover 98% of
> rust-exp.y, and 82% of rust-lang.c -- mostly missing things like
> rust_print_subexp; I intentionally didn't write tests for the
> expression-dumping debug functions.

Impressive.

> 
> I wrote most of the code, but Manish Goregaokar did some as well --
> more than enough to require an assignment.  Both of our copyright
> assignments are in process.
> 
> I've built the series both with gcc and with g++.
> 

Thank you.

> I'd like to make a new rust component in bugzilla once this is
> approved.

I think I can make this for you, if you need it.

> If anybody cares, I have a list of the ugly bits in gdb I encountered
> while writing this series.  I think it's all generally well known
> though.

I'd be curious.

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-04-27 11:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  2:50 Tom Tromey
2016-04-27  2:50 ` [PATCH 5/8] Add array start and end strings to generic_val_print_decorations Tom Tromey
2016-04-27 11:40   ` Pedro Alves
2016-04-27  2:50 ` [PATCH 1/8] Add DW_LANG_Rust and DW_LANG_Rust_old Tom Tromey
2016-04-27 11:44   ` Pedro Alves
2016-04-27  2:50 ` [PATCH 4/8] Add self-test framework to gdb Tom Tromey
2016-04-27 11:40   ` Pedro Alves
2016-04-27 17:58     ` Tom Tromey
2016-04-27  2:50 ` [PATCH 7/8] Update gdb test suite for Rust Tom Tromey
2016-04-27 11:44   ` Pedro Alves
2016-04-27  2:50 ` [PATCH 8/8] Add Rust documentation Tom Tromey
2016-04-27  7:10   ` Eli Zaretskii
2016-04-27  2:50 ` [PATCH 6/8] Add support for the Rust language Tom Tromey
2016-04-27 11:43   ` Pedro Alves
2016-04-27 11:49     ` Pedro Alves
2016-04-27 18:27     ` Tom Tromey
2016-04-27 18:36       ` Pedro Alves
2016-04-27 19:52       ` Tom Tromey
2016-04-27  2:50 ` [PATCH 2/8] Fix latent yacc-related bug in gdb/Makefile.in init.c rule Tom Tromey
2016-04-27 11:38   ` Pedro Alves
2016-04-27  2:50 ` [PATCH 3/8] Make gdb expression debugging handle OP_F90_RANGE Tom Tromey
2016-04-27 11:38   ` Pedro Alves
2016-04-27 11:47 ` Pedro Alves [this message]
2016-04-27 16:22   ` [PATCH 0/8] Add Rust language support Tom Tromey
2016-04-27 18:23     ` Pedro Alves
2016-04-27 21:56   ` 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=5720A6B6.8010505@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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