public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order Date: Sun, 06 Aug 2023 14:51:11 +0000 [thread overview] Message-ID: <bug-30727-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30727 Bug ID: 30727 Summary: [gdb/symtab] Maintenance command to reverse DIE reading order Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- It could be useful to read a CU in reverse top-level DIE order, turning backward references into forward references and vice versa. Likewise for CU reading order, turning backward inter-CU references into forward inter-CU references. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-08-06 14:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-06 14:51 vries at gcc dot gnu.org [this message] 2023-08-06 15:04 ` [Bug symtab/30727] " tromey at sourceware dot org 2023-08-06 16:19 ` vries 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-30727-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).