From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, Yao Qi <qiyaoltc@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] Move logic out of symbol_find_demangled_name
Date: Tue, 07 Jun 2016 15:12:00 -0000 [thread overview]
Message-ID: <871t496nk4.fsf@tromey.com> (raw)
In-Reply-To: <9b062e13-3541-b122-2da8-1c61fe7fe55b@redhat.com> (Pedro Alves's message of "Tue, 7 Jun 2016 15:27:20 +0100")
Pedro> Before, this would set language to language_cplus, even if the
Pedro> symbol's language was Rust.
[...]
Pedro> However, this no longer forces C++, is that intended?
I think the old code was in error.
Pedro> Also, before we'd check whether gdb_demangle returned not-NULL,
Pedro> before taking the language, but now several languages
Pedro> return 1 even if gdb_demangle returns NULL:
Sorry about that. I'll fix up the patch a bit more.
Tom
next prev parent reply other threads:[~2016-06-07 15:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 14:49 [RFA 0/3] minor language cleanups Tom Tromey
2016-06-04 14:49 ` [RFA 1/3] Use VEC for filename_language_table Tom Tromey
2016-06-06 13:06 ` Yao Qi
2016-06-04 14:49 ` [RFA 2/3] Move filename extensions into language_defn Tom Tromey
2016-06-06 13:23 ` Yao Qi
2016-06-06 21:04 ` Tom Tromey
2016-06-07 15:51 ` Yao Qi
2016-06-04 14:49 ` [RFA 3/3] Move logic out of symbol_find_demangled_name Tom Tromey
2016-06-06 14:15 ` Yao Qi
2016-06-07 11:41 ` Tom Tromey
2016-06-07 14:27 ` Pedro Alves
2016-06-07 15:12 ` Tom Tromey [this message]
2016-06-13 13:35 ` Pedro Alves
2016-06-17 8:28 ` Tom Tromey
2016-06-17 12:25 ` Pedro Alves
2016-06-17 12:36 ` Tom Tromey
2016-06-17 13:50 ` Pedro Alves
2016-06-24 3:15 ` Tom Tromey
2016-06-07 14:03 ` Pedro Alves
2016-06-08 2:14 ` Tom Tromey
2016-06-08 4:03 ` Tom Tromey
2016-06-13 13:35 ` Pedro Alves
2016-06-17 8:41 ` Tom Tromey
2016-06-17 12:28 ` 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=871t496nk4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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