From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/4] [COVER-LETTER] Use task size balancing in cooked index creation
Date: Fri, 22 Jul 2022 19:03:42 +0200 [thread overview]
Message-ID: <20220722170345.24713-1-tdevries@suse.de> (raw)
Reworking of "[gdbsupport] Use task size in parallel_for_each", submitted
earlier here (
https://sourceware.org/pipermail/gdb-patches/2022-July/190868.html ).
Note that this series assumes "Introduce gdb::make_function_view" as posted
here ( https://sourceware.org/pipermail/gdb-patches/2022-July/190992.html ).
---
gdb/COVER-LETTER | 0
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 gdb/COVER-LETTER
diff --git a/gdb/COVER-LETTER b/gdb/COVER-LETTER
new file mode 100644
index 00000000000..e69de29bb2d
base-commit: 0d119fdec7883d2e8ee59ee1369c96788f9b18a5
--
2.35.3
next reply other threads:[~2022-07-22 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:03 Tom de Vries [this message]
2022-07-22 17:03 ` [PATCH 2/4] [gdbsupport] Add task size parameter in parallel_for_each Tom de Vries
2022-07-22 17:03 ` [PATCH 3/4] [gdb/symtab] Use task size in parallel_for_each in dwarf2_build_psymtabs_hard Tom de Vries
2022-07-22 17:03 ` [PATCH 4/4] [gdb] Add unit test for gdb::sequential_for_each Tom de Vries
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=20220722170345.24713-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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).