public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/29942] New: Read some DWARF purely in background Date: Sun, 25 Dec 2022 21:21:41 +0000 [thread overview] Message-ID: <bug-29942-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29942 Bug ID: 29942 Summary: Read some DWARF purely in background Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Currently, dwarf2_build_psymtabs_hard works synchronously: it sends some work to worker threads, but it waits for all work to be completed before proceeding. However, it doesn't have to work this way. Instead, it could start reading immediately; and then after starting the background tasks, it could store a future that would then be waited on by cooked_index_functions::read_partial_symbols. I think the main benefit to doing this would be that "attach" might appear to be faster. In particular work like downloading from debuginfod could be done while other threads are scanning the DWARF. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-25 21:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-25 21:21 tromey at sourceware dot org [this message] 2022-12-25 21:21 ` [Bug symtab/29942] " tromey at sourceware dot org 2022-12-25 21:22 ` tromey at sourceware dot org 2022-12-26 5:53 ` tromey at sourceware dot org 2022-12-27 16:30 ` tromey at sourceware dot org 2023-08-13 15:37 ` tromey at sourceware dot org 2023-08-18 17:49 ` tromey at sourceware dot org 2023-08-19 7:11 ` sam at gentoo dot org 2023-08-23 20:02 ` tromey at sourceware dot org 2023-10-04 12:47 ` tromey at sourceware dot org 2023-11-12 23:27 ` tromey at sourceware dot org 2024-01-09 1:46 ` cvs-commit at gcc dot gnu.org 2024-01-09 1:48 ` tromey at sourceware dot org
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=bug-29942-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).