From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dje@google.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] printing/setting flag register fields
Date: Sat, 19 Sep 2009 07:07:00 -0000 [thread overview]
Message-ID: <200909190707.n8J770nt005979@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20090918235632.0DDC6843AC@ruffy.mtv.corp.google.com> (dje@google.com)
> Date: Fri, 18 Sep 2009 16:56:32 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> "pty $eflags" output is a bit hard to read, but I thought I'd play
> with printing the field names *and* field positions.
There is a nasty problem here that bit numbering is inconsistent
across architectures. People typically call the LSB '0', but on
powerpc or hppa people start numbering from the MSB.
Also, how would you handle multi-bit fields?
next prev parent reply other threads:[~2009-09-19 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 23:57 Doug Evans
2009-09-19 7:07 ` Mark Kettenis [this message]
2009-09-19 7:38 ` Andreas Schwab
2009-09-20 18:00 ` Daniel Jacobowitz
2009-09-20 18:35 ` Doug Evans
2009-09-20 20:27 ` Daniel Jacobowitz
2009-09-21 16:43 ` Tom Tromey
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=200909190707.n8J770nt005979@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dje@google.com \
--cc=gdb-patches@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: 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