From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH v3 0/2] Write DWARF index cache files in background
Date: Fri, 24 Feb 2023 11:46:24 -0700 [thread overview]
Message-ID: <87k006j3zz.fsf@tromey.com> (raw)
In-Reply-To: <20221219164558.378363-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Mon, 19 Dec 2022 09:45:56 -0700")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Here's v3 of the patches to write the DWARF index in the background.
Tom> v2 was here:
Tom> https://sourceware.org/pipermail/gdb-patches/2022-June/189889.html
Tom> This hides a user-noticeable pause when the feature is enabled. (Note
Tom> that, when the feature is used in batch mode, the pause is still
Tom> seen.)
Tom> This version of the series fixes a possible race that I found in v2.
Tom> Essentially, the index-writing background job must be started after
Tom> all the finalization tasks have started. There's a comment in the
Tom> code explaining this.
I'm checking this in now.
Tom
next prev parent reply other threads:[~2023-02-24 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 16:45 Tom Tromey
2022-12-19 16:45 ` [PATCH v3 1/2] Only use the per-BFD object to write a DWARF index Tom Tromey
2022-12-19 16:45 ` [PATCH v3 2/2] Write the DWARF index in the background Tom Tromey
2023-02-24 18:46 ` Tom Tromey [this message]
2023-02-24 21:44 ` [PATCH v3 0/2] Write DWARF index cache files in background Simon Marchi
2023-03-02 15:51 ` Tom Tromey
2023-03-03 16:41 ` Tom Tromey
2023-03-03 17:22 ` Simon Marchi
2023-03-03 17:29 ` Tom Tromey
2023-03-03 17:52 ` Simon Marchi
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=87k006j3zz.fsf@tromey.com \
--to=tromey@adacore.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).