From: Dmitry Neverov <dmitry.neverov@jetbrains.com>
To: gdb-patches@sourceware.org
Cc: dmitry.neverov@jetbrains.com
Subject: [PATCH v3][PR symtab/30520 v2 3/4] gdb/symtab: compute match_type outside the loop
Date: Wed, 8 May 2024 22:22:18 +0200 [thread overview]
Message-ID: <20240508202219.3584915-3-dmitry.neverov@jetbrains.com> (raw)
In-Reply-To: <20240508202219.3584915-1-dmitry.neverov@jetbrains.com>
It will be used for all segments in a qualified name,
not only the last one.
---
gdb/dwarf2/read.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index 8da0af01d72..48d5dc11d1d 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -16637,6 +16637,9 @@ cooked_index_functions::expand_symtabs_matching
language_ada
};
+ symbol_name_match_type match_type
+ = lookup_name_without_params.match_type ();
+
for (enum language lang : unique_styles)
{
std::vector<std::string_view> name_vec
@@ -16693,8 +16696,6 @@ cooked_index_functions::expand_symtabs_matching
"x::a::b". */
if (symbol_matcher == nullptr)
{
- symbol_name_match_type match_type
- = lookup_name_without_params.match_type ();
if ((match_type == symbol_name_match_type::FULL
|| (lang != language_ada
&& match_type == symbol_name_match_type::EXPRESSION)))
--
2.40.1
next prev parent reply other threads:[~2024-05-08 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 20:22 [PATCH v3][PR symtab/30520 v2 1/4] gdb/symtab: check name matches before expanding a CU Dmitry Neverov
2024-05-08 20:22 ` [PATCH v3][PR symtab/30520 v2 2/4] gdb/symtab: reuse last segment lookup name info by creating it outside the loop Dmitry Neverov
2024-05-08 20:22 ` Dmitry Neverov [this message]
2024-05-08 20:22 ` [PATCH v3][PR symtab/30520 v2 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name Dmitry Neverov
2024-05-10 18:39 ` [PATCH v3][PR symtab/30520 v2 1/4] gdb/symtab: check name matches before expanding a CU Tom Tromey
2024-05-17 14:01 ` Tom Tromey
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=20240508202219.3584915-3-dmitry.neverov@jetbrains.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).