public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/99178] Emit .debug_names Date: Mon, 22 Feb 2021 09:00:29 +0000 [thread overview] Message-ID: <bug-99178-4-Kjujt0qmRe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99178-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99178 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |mark at gcc dot gnu.org, | |vries at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'm not sure if it is a good idea. The indexes are useful when they cover the whole binary or library, when each TU has its own index, then I don't see how it is helpful for the consumer to search each TU's index compared to walking the DIEs. I think .debug_names should be created during linking or post-linking, so ld, dwz or gdb.
next prev parent reply other threads:[~2021-02-22 9:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-20 0:20 [Bug debug/99178] New: " tromey at gcc dot gnu.org 2021-02-22 8:44 ` [Bug debug/99178] " rguenth at gcc dot gnu.org 2021-02-22 9:00 ` jakub at gcc dot gnu.org [this message] 2021-02-22 21:40 ` mark at gcc dot gnu.org 2024-01-10 1:20 ` dblaikie at gmail dot com 2024-01-10 2:47 ` tromey at gcc dot gnu.org 2024-01-10 18:51 ` dblaikie at gmail dot com 2024-01-10 20:31 ` tromey at gcc dot gnu.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-99178-4-Kjujt0qmRe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).