From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdbsupport] Use task size in parallel_for_each
Date: Fri, 22 Jul 2022 12:07:16 +0100 [thread overview]
Message-ID: <e8159be7-8067-c2de-069b-ccc550dea6f0@palves.net> (raw)
In-Reply-To: <a624f5a9-72b8-4dc6-7458-f1e705d7b9c0@palves.net>
On 2022-07-22 1:03 a.m., Pedro Alves wrote:
> I think the best is to introduce a gdb::make_function_view function,
> so that you can do this:
>
> diff --git c/gdb/dwarf2/read.c w/gdb/dwarf2/read.c
> index 23c3873cba6..255b955a54c 100644
> --- c/gdb/dwarf2/read.c
> +++ w/gdb/dwarf2/read.c
> @@ -7101,7 +7101,7 @@ dwarf2_build_psymtabs_hard (dwarf2_per_objfile *per_objfile)
> }
> }
> return result_type (thread_storage.release (), std::move (errors));
> - }, task_size);
> + }, gdb::make_function_view (task_size));
>
> /* Only show a given exception a single time. */
> std::unordered_set<gdb_exception> seen_exceptions;
>
> I've got that working here. I'll post it tomorrow.
Posted here:
[PATCH 0/1] Introduce gdb::make_function_view
https://sourceware.org/pipermail/gdb-patches/2022-July/190991.html
next prev parent reply other threads:[~2022-07-22 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 19:42 Tom de Vries via Gdb-patches
2022-07-21 17:35 ` Pedro Alves
2022-07-21 20:23 ` Tom de Vries via Gdb-patches
2022-07-22 0:03 ` Pedro Alves
2022-07-22 11:07 ` Pedro Alves [this message]
2022-07-22 17:07 ` Tom de Vries via Gdb-patches
2022-07-22 19:08 ` Tom Tromey
2022-07-22 19:38 ` Simon Marchi via Gdb-patches
2022-07-23 3:17 ` Tom Tromey
2022-07-22 21:21 ` Tom Tromey
2022-07-23 6:51 ` Tom de Vries via Gdb-patches
2022-07-31 8:38 ` Tom de Vries via Gdb-patches
2022-07-23 5:55 ` Tom de Vries via Gdb-patches
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=e8159be7-8067-c2de-069b-ccc550dea6f0@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.com \
/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