From: Richard Bunt <richard.bunt@linaro.org>
To: gdb-patches@sourceware.org
Subject: [PATCH v4] gdb: Enable early init of thread pool size
Date: Fri, 24 Nov 2023 16:13:19 +0000 [thread overview]
Message-ID: <20231124161321.572511-1-richard.bunt@linaro.org> (raw)
Updates in v4.
Clamped the default number of worker threads to eight. I'm ok with this as GDB
can always be configured to use a higher number of work threads if the use case
demands it.
I have included Andrew's patch in the set as they'll need to be pushed
together. It has the following adjustments over the original version
* Commit message nit: nullput -> nullptr
* Rebased to trunk and swapped to std:make_unique.
* I'm not quite sure on the etiquette here but: Added tested by git trailer.
As always, happy to work on any further comments.
next reply other threads:[~2023-11-24 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 16:13 Richard Bunt [this message]
2023-11-24 16:13 ` [PATCH v4 1/2] gdb: install CLI uiout while processing early init files Richard Bunt
2023-11-24 16:13 ` [PATCH v4 2/2] gdb: Enable early init of thread pool size Richard Bunt
2023-12-06 11:26 ` [PUSHED] gdb: fix libstdc++ assert caused by invalid use of std::clamp Andrew Burgess
2023-11-27 20:23 ` [PATCH v4] gdb: Enable early init of thread pool size Tom Tromey
2023-12-05 7:56 ` Tom de Vries
2023-12-05 9:35 ` Richard Bunt
2023-12-05 13:10 ` Richard Bunt
2023-12-05 14:39 ` 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=20231124161321.572511-1-richard.bunt@linaro.org \
--to=richard.bunt@linaro.org \
--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).