From: Tom Tromey <tom@tromey.com>
To: Dmitry Neverov <dmitry.neverov@jetbrains.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test
Date: Wed, 07 Feb 2024 13:25:44 -0700 [thread overview]
Message-ID: <87y1bw9g3b.fsf@tromey.com> (raw)
In-Reply-To: <20240125084404.3536456-1-dmitry.neverov@jetbrains.com> (Dmitry Neverov's message of "Thu, 25 Jan 2024 09:44:04 +0100")
>>>>> "Dmitry" == Dmitry Neverov <dmitry.neverov@jetbrains.com> writes:
Dmitry> The symbol_name_match_type::SEARCH_NAME cannot be used because
Dmitry> demangle_for_lookup_info doesn't initialize a demangled name
Dmitry> for it which makes a subsequent name matching to fail.
I don't think I understand this comment, but anyway shouldn't this patch
simply be folded into an earlier one in the series?
I read through these and they seem basically reasonable to me -- in line
with what I was hoping for. There are some minor formatting issues.
You didn't mention what testing you did, so I am curious about that.
thanks,
Tom
next prev parent reply other threads:[~2024-02-07 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 17:03 [RFC v2][PR symtab/30520 1/4] gdb/symtab: check name matches before expanding a CU Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 2/4] gdb/symtab: reuse last segment lookup name info Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 3/4] gdb/symtab: compute match_type outside the loop Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name Dmitry Neverov
2024-01-25 8:44 ` [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test Dmitry Neverov
2024-02-07 20:25 ` Tom Tromey [this message]
2024-02-09 16:32 ` Dmitry Neverov
2024-02-09 19:38 ` Tom Tromey
2024-03-18 16:35 ` Dmitry Neverov
2024-03-18 17:58 ` Tom Tromey
2024-03-19 12:16 ` Dmitry Neverov
2024-03-22 17:29 ` Tom Tromey
2024-05-04 1:20 ` Joel Brobecker
2024-05-06 14:32 ` Dmitry Neverov
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=87y1bw9g3b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dmitry.neverov@jetbrains.com \
--cc=gdb-patches@sourceware.org \
/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