public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "robert.pirvu at cyberthorstudios dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/31448] [Feature Request] Register's bitfields MI Commands Date: Wed, 06 Mar 2024 12:05:28 +0000 [thread overview] Message-ID: <bug-31448-4717-pStokxpLPR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31448-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31448 --- Comment #2 from Robert Pîrvu <robert.pirvu at cyberthorstudios dot com> --- Register View uses two MI Commands to populate the view with registers. One command which returns the names of the registers, and another which returns the positions and values of the registers. I wanted to have a bit of consistency with the commands and that is why I proposed to have something similar, one command to return the names of bitfields and one for the values. And it will be a lot easier for this to work with the existing parsers used by the Register View. Maybe instead of implementing a new command for getting the bitfield's names, we can use the same approach by adding a --with-bitfields option to the -data-list-register-name MI Command. It might be better than having to create a new MI Command which will be used only in this case. And I forgot to mention this, in case the register doesn't have bitfields, then the bitfields list will be empty. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-03-06 12:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-04 14:16 [Bug mi/31448] New: " robert.pirvu at cyberthorstudios dot com 2024-03-04 15:29 ` [Bug mi/31448] " tromey at sourceware dot org 2024-03-06 12:05 ` robert.pirvu at cyberthorstudios dot com [this message]
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-31448-4717-pStokxpLPR@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).