From: Ian Lance Taylor <iant@google.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: gcc@gcc.gnu.org
Subject: Re: C99 Status - inttypes.h
Date: Thu, 21 Jul 2011 22:45:00 -0000 [thread overview]
Message-ID: <mcripqvw98h.fsf@coign.corp.google.com> (raw)
In-Reply-To: <20110721180549.47be5d76ef4813df693d2bf0@starynkevitch.net> (Basile Starynkevitch's message of "Thu, 21 Jul 2011 18:05:49 +0200")
Basile Starynkevitch <basile@starynkevitch.net> writes:
> This brings another question. Can a GCC pass use intptr_t (the standard int of the same
> size as a void* pointer)? This is quite useful, for instance when one wants to compute an
> hash, or a unique sorted rank (to be used inside B-trees) from the address of a gimple
> or a tree.
Yes. There are a number of uses of intptr_t already in the gcc source
code. We can get away with this because the configure script uses
AC_TYPE_INTPTR_T (via GCC_STDINT_TYPES).
Ian
prev parent reply other threads:[~2011-07-21 22:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 14:30 Diogo Sousa
2011-07-21 15:52 ` Joseph S. Myers
2011-07-21 18:13 ` Joe Buck
2011-07-22 11:05 ` Diogo Sousa
2011-07-22 13:03 ` Paulo J. Matos
2011-07-22 15:38 ` Joern Rennecke
2011-07-22 17:43 ` Paulo J. Matos
2011-07-22 20:12 ` James Dennett
2011-07-23 19:29 ` Weddington, Eric
2011-07-23 21:10 ` Eric Botcazou
2011-07-23 22:47 ` Weddington, Eric
2011-08-21 19:27 ` Gerald Pfeifer
2011-09-25 13:00 ` Joern Rennecke
2011-09-25 22:49 ` Joseph S. Myers
2011-09-25 22:53 ` Gerald Pfeifer
2011-09-26 7:11 ` Joseph S. Myers
2011-07-21 16:06 ` Basile Starynkevitch
2011-07-21 22:45 ` Ian Lance Taylor [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=mcripqvw98h.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).