public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vcollod at nvidia dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/25663] dwarf2_name caching bug Date: Thu, 12 Mar 2020 21:01:48 +0000 [thread overview] Message-ID: <bug-25663-4717-eD3cXXynHr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25663-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25663 --- Comment #7 from Victor Collod <vcollod at nvidia dot com> --- (In reply to Tom Tromey from comment #6) > It just would be better if it cached the stripped name, > like partial_die_info::fixup does. I'm not sure I understand why that couldn't be done, it some code relying on the content of the cache? > Also, canonicalizing the demangled name on the linkage > name attribute just seems bad. Like, what if we want > to examine the actual linkage name for some reason? That's the way the code currently works ¯\_(ツ)_/¯ > Anyway this seems like a mild improvement, WDYT? It's indeed much better! -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-12 21:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-12 16:37 [Bug gdb/25663] New: " vcollod at nvidia dot com 2020-03-12 16:38 ` [Bug gdb/25663] " vcollod at nvidia dot com 2020-03-12 20:22 ` tromey at sourceware dot org 2020-03-12 20:25 ` tromey at sourceware dot org 2020-03-12 20:27 ` tromey at sourceware dot org 2020-03-12 20:28 ` vcollod at nvidia dot com 2020-03-12 20:50 ` tromey at sourceware dot org 2020-03-12 20:55 ` tromey at sourceware dot org 2020-03-12 21:01 ` vcollod at nvidia dot com [this message] 2020-03-12 21:21 ` tromey at sourceware dot org 2020-03-13 15:20 ` tromey at sourceware dot org 2020-03-16 21:03 ` cvs-commit at gcc dot gnu.org 2024-01-05 12:50 ` ssbssa at sourceware dot org 2024-01-10 18:38 ` 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-25663-4717-eD3cXXynHr@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).