From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Thu, 26 May 2005 03:39:00 -0000 [thread overview]
Message-ID: <uu0kqy7so.fsf@gnu.org> (raw)
In-Reply-To: <17045.1379.28193.987032@farnswood.snap.net.nz> (message from Nick Roberts on Thu, 26 May 2005 11:08:19 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Thu, 26 May 2005 11:08:19 +1200
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
>
> > You know it's a number - it's going to stay a number. A function to
> > turn one hex number into a regular expression that would match it with
> > leading zeros wouldn't be much work.
>
> If you are saying that the address formats will only differ in their number of
> leading zeros, and not in other ways, then that is good enough for my purposes.
Well, it's a number, right? What else can possibly change in the
address format that leaves the numeric value unmodified? The only
other thing, besides leading zeros, that I can think of is sign
extension in some weird 32/64 bit situations. But that's a theory, I
don't even know if it's possible in practice. So I'd say leading
zeros is all you need to worry about for now.
next prev parent reply other threads:[~2005-05-26 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 3:18 Nick Roberts
2005-05-25 3:37 ` Daniel Jacobowitz
2005-05-25 3:51 ` Nick Roberts
2005-05-25 18:00 ` Eli Zaretskii
2005-05-25 21:10 ` Nick Roberts
2005-05-25 21:28 ` Daniel Jacobowitz
2005-05-25 23:11 ` Nick Roberts
2005-05-26 3:39 ` Eli Zaretskii [this message]
2005-05-26 3:46 ` Daniel Jacobowitz
2005-05-26 4:12 ` Nick Roberts
2005-05-25 4:12 ` Nick Roberts
2005-05-25 5:27 ` M.M. Kettenis
2005-05-25 5:48 ` Nick Roberts
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=uu0kqy7so.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).