From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Flags fields in register xml descriptions are suboptimal: What to do?
Date: Thu, 04 Feb 2016 15:11:00 -0000 [thread overview]
Message-ID: <56B36A3A.5060109@redhat.com> (raw)
In-Reply-To: <8660y4pmh1.fsf@gmail.com>
On 02/04/2016 02:40 PM, Yao Qi wrote:
>>
>> Also, I'd like to print flags even if they're zero. E.g.,
>>
>> (gdb) i r cpsr
>> cpsr 0xa0000020 123456 [ Z !C N !V EL=1 ... ]
>>
>> or some such.
>> IOW, instead of not printing fields that are zero/false/off,
>> print them as "!FIELD".
>
> I am not sure of this one.
Me neither. I don't think I'd like it, personally. I find it easier to
spot the rogue TF or some such if only the set bits are displayed.
And I imagine that with a 64-bit flags register that would result in
a very long string hard to grok.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-02-04 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 0:08 Doug Evans
2016-02-04 14:41 ` Yao Qi
2016-02-04 15:11 ` Pedro Alves [this message]
2016-02-04 15:19 ` Pedro Alves
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=56B36A3A.5060109@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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: link
Be 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