From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 6/8] Add support for the Rust language
Date: Wed, 27 Apr 2016 19:52:00 -0000 [thread overview]
Message-ID: <87r3dqbzii.fsf@tromey.com> (raw)
In-Reply-To: <87y47yc3ge.fsf@tromey.com> (Tom Tromey's message of "Wed, 27 Apr 2016 12:27:13 -0600")
>>> + /* Rust does not currently emit DW_LANG_Rust or DW_LANG_Rust_old.
Pedro> "Currently" is a moving target. Could you replace it with some
Pedro> version number or some such?
Tom> It turns out that the patch to drop DW_LANG_Rust didn't go in yet, since
Tom> it causes an assertion failure in LLVM. This will probably shake out
Tom> before the copyright assignments are done anyway.
I'm thinking I will just drop this hunk. Even if the patch does go in
soon, it will only be in nightly, and that's known not to work yet for
other reasons -- and since other changes might need to be done at some
point for nightly, we can always restore this producer sniffing stuff
later as well.
Tom
next prev parent reply other threads:[~2016-04-27 19:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 2:50 [PATCH 0/8] Add Rust language support 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 7/8] Update gdb test suite for Rust 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 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 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 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 [this message]
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 3/8] Make gdb expression debugging handle OP_F90_RANGE Tom Tromey
2016-04-27 11:38 ` Pedro Alves
2016-04-27 11:47 ` [PATCH 0/8] Add Rust language support Pedro Alves
2016-04-27 16:22 ` 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=87r3dqbzii.fsf@tromey.com \
--to=tom@tromey.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