public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Dmitry Neverov <dmitry.neverov@jetbrains.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v3][PR symtab/30520 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name
Date: Mon, 6 May 2024 17:23:51 +0200	[thread overview]
Message-ID: <CAEY59_JpQWTtKv7HzCQ0mzK_jURL3bEsMPLKmqJRhY0uXg1WGw@mail.gmail.com> (raw)
In-Reply-To: <20240506150920.1220092-4-dmitry.neverov@jetbrains.com>

I've run tests on x86-64 linux. The only unexpected failure was

FAIL: gdb.base/empty-host-env-vars.exp: env_var_name=HOME: show
index-cache directory

But it doesn't seem to be related to this patch.

--
Dmitry

  reply	other threads:[~2024-05-06 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 15:09 [PATCH v3][PR symtab/30520 1/4] gdb/symtab: check name matches before expanding a CU Dmitry Neverov
2024-05-06 15:09 ` [PATCH v3][PR symtab/30520 2/4] gdb/symtab: reuse last segment lookup name info by creating it outside the loop Dmitry Neverov
2024-05-07 17:09   ` Tom Tromey
2024-05-06 15:09 ` [PATCH v3][PR symtab/30520 3/4] gdb/symtab: compute match_type " Dmitry Neverov
2024-05-07 17:10   ` Tom Tromey
2024-05-06 15:09 ` [PATCH v3][PR symtab/30520 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name Dmitry Neverov
2024-05-06 15:23   ` Dmitry Neverov [this message]
2024-05-07 17:26   ` Tom Tromey
2024-05-07 17:03 ` [PATCH v3][PR symtab/30520 1/4] gdb/symtab: check name matches before expanding a CU Tom Tromey
2024-05-08 11:32   ` Dmitry.Neverov
2024-05-08 15:48     ` Tom Tromey
2024-05-09  5:55       ` 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=CAEY59_JpQWTtKv7HzCQ0mzK_jURL3bEsMPLKmqJRhY0uXg1WGw@mail.gmail.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).