Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Andrew Burgess" <aburgess@broadcom.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING (docs)] Re: [PATCH] [1/2] Add new 'z' format for print command
Date: Wed, 24 Jul 2013 17:08:00 -0000	[thread overview]
Message-ID: <51F00A06.6010402@broadcom.com> (raw)
In-Reply-To: <83bo5rx59d.fsf@gnu.org>

On 24/07/2013 6:00 PM, Eli Zaretskii wrote:
>> Date: Wed, 24 Jul 2013 16:16:01 +0100
>> From: "Andrew Burgess" <aburgess@broadcom.com>
>> cc: gdb-patches@sourceware.org
>>
>> On 24/07/2013 3:34 PM, Eli Zaretskii wrote:
>>
>>> More importantly, I have a difficulty understanding what does
>>> "hexadecimal zero padded to the size ..." mean.  More accurately, if
>>> my interpretation of what you say (that 'z' produces "00"s for
>>> non-existing data, then why does this "padding" make sense, when we
>>> are targeting a human consumer?
>>
>> I'm not sure I agree with the "non-existing data" part of your
>> statement, for example a 4-byte register containing the value 1 (one)
>> when printed with /x would print 0x1, with /z it would print 0x00000001,
>> surely the leading 0s do exist, we just normally don't print them.
> 
> Then please say "zero padded on the left".  I thought you were talking
> about padding at the right.  Sorry for my misunderstanding.

OK.  I'll re-word that tomorrow, do you want to see a revised patch
before I commit?

Thanks for your time,
Andrew



  reply	other threads:[~2013-07-24 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 17:30 Andrew Burgess
2013-07-10 17:30 ` Tom Tromey
2013-07-11 15:20   ` Andrew Burgess
2013-07-18  7:57     ` Andrew Burgess
2013-07-24 10:07 ` [PING (docs)] " Andrew Burgess
2013-07-24 14:35   ` Eli Zaretskii
2013-07-24 15:16     ` Andrew Burgess
2013-07-24 17:00       ` Eli Zaretskii
2013-07-24 17:08         ` Andrew Burgess [this message]
2013-07-24 17:43           ` Eli Zaretskii
2013-07-25 10:18             ` Andrew Burgess

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=51F00A06.6010402@broadcom.com \
    --to=aburgess@broadcom.com \
    --cc=eliz@gnu.org \
    --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