From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [unavailable values part 1, 03/17] expose list of available ranges to common code
Date: Tue, 15 Feb 2011 21:02:00 -0000 [thread overview]
Message-ID: <20110215204421.GA17644@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201102151859.03901.pedro@codesourcery.com>
On Tue, 15 Feb 2011 19:59:03 +0100, Pedro Alves wrote:
> As for what type for use then instead of CORE_ADDR, we traditionaly
> use LONGEST/ULONGEST throughout, AFAICS. I guess nobody ever saw
> a real need to come up with a special type for it.
OK, I understand and agree with the difference now, thanks for the
explanation.
I will try to introduce some CORE_SIZE_T or similar type when my future
patches need it.
Thanks,
Jan
prev parent reply other threads:[~2011-02-15 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 14:29 Pedro Alves
2011-02-14 11:59 ` Jan Kratochvil
2011-02-14 19:54 ` Pedro Alves
2011-02-14 21:44 ` Jan Kratochvil
2011-02-15 18:42 ` Tom Tromey
2011-02-15 19:14 ` Pedro Alves
2011-02-15 21:02 ` Jan Kratochvil [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=20110215204421.GA17644@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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