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: [PATCH] Re: Your addition of BT_SSIZE

From: "Zack Weinberg" <zack at codesourcery dot com>
To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
Cc: Roger Sayle <roger at eyesopen dot com>, Diego Novillo <dnovillo at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Tue, 19 Aug 2003 09:31:31 -0700
Subject: Re: [PATCH] Re: Your addition of BT_SSIZE
References: <Pine.LNX.4.44.0308182227130.22816-100000@www.eyesopen.com><Pine.LNX.4.56.0308191007180.5024@kern.srcf.societies.cam.ac.uk><Pine.LNX.4.56.0308191029010.7200@kern.srcf.societies.cam.ac.uk>

"Joseph S. Myers" <jsm@polyomino.org.uk> writes:

>  ... so ssize_t (the POSIX type, which I see is now used for strfmon now
> that is handled as a built-in function, being the origin of the problem
> behind this patch) should be represented internally as something
> *separate* from the signed version of size_t (defaulting to the signed
> version of size_t, with a facility for targets to change this added if a
> supported target is found on which they differ).

How about we worry about this only when such a target actually turns
up in real life?

zw

Follow-Ups:
- Re: [PATCH] Re: Your addition of BT_SSIZE
  - From: Joseph S. Myers

References:
- [PATCH] Re: Your addition of BT_SSIZE
  - From: Roger Sayle
- Re: [PATCH] Re: Your addition of BT_SSIZE
  - From: Joseph S. Myers
- Re: [PATCH] Re: Your addition of BT_SSIZE
  - From: Joseph S. Myers

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