This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [libstdc++] intptr_t usage

From: Mark Mitchell <mark at codesourcery dot com>
To: Richard Henderson <rth at redhat dot com>, Paolo Carlini <pcarlini at suse dot de>, libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Fri, 30 Mar 2007 10:20:57 -0700
Subject: Re: [libstdc++] intptr_t usage
References: <20070327220453.GA4342@redhat.com> <46099F40.4060409@suse.de> <20070327232910.GB3360@redhat.com> <4609AB4A.6040206@suse.de> <20070327235506.GA4679@redhat.com>

Richard Henderson wrote:
> On Wed, Mar 28, 2007 at 01:39:54AM +0200, Paolo Carlini wrote:
>> Seriously, I'm thinking that, in any case, considering only unsigned 
>> long and something bigger - unsigned long long - we cannot regress, 
>> right?
> 
> Probably not.  I'll leave this up to you then.

How about adding __INTPTR_TYPE__ to the builtin defines, like
__SIZE_TYPE__ and __PTRDIFF_TYPE__?  (Or, lazily, how about using
__PTRDIFF_TYPE__ as I would expect that to be the same as intptr_t on
most platforms.)

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

Follow-Ups:
- Re: [libstdc++] intptr_t usage
  - From: Paolo Carlini

References:
- [libstdc++]
  - From: Richard Henderson
- Re: [libstdc++]
  - From: Paolo Carlini
- Re: [libstdc++] intptr_t usage
  - From: Richard Henderson
- Re: [libstdc++] intptr_t usage
  - From: Paolo Carlini
- Re: [libstdc++] intptr_t usage
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]