From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Egger <Christoph.Egger@amd.com>
Subject: Re: size_t and printk and Xen
Date: Mon, 13 Oct 2008 12:02:09 +0200
Message-ID: <200810131202.09673.Christoph.Egger@amd.com>
References: <9aa34f3c-2ab0-4425-b4d4-0994cc7fa6fb@default>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <9aa34f3c-2ab0-4425-b4d4-0994cc7fa6fb@default>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>, Keir Fraser <keir.fraser@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Sunday 12 October 2008 20:12:33 Dan Magenheimer wrote:
> > >> I'm no particular fan of size_t in hypervisor interfaces
> > >> though. So, for
> > >> example, switching xmalloc() interfaces to use unsigned int
> > >> instead would be
> > >> fine by me, and this would sidestep the issue perhaps?
> > >
> > > I think C99 size_t may have compile-time type-checking uses so
> > > I'd be hesitant to remove it entirely.
> >
> > Can you give a concrete example of how it helps us to use it
> > within the
> > xmalloc interfaces? As far as I'm aware it's not useful at
> > all, but I could
> > certainly be wrong as this aspect of the C spec is not
> > something I've ever
> > really investigated.
>
> No, I can't.  IIRC it has something to do with portability to
> unusual platforms.  Perhaps someone else with more knowledge
> of C99 can comment on whether size_t is useful in Xen or we
> should just avoid using it.

NetBSD uses %zi for ssize_t and %zu for size_t.
%z doesn't exist.

Christoph

=2D-=20
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Gesch=E4ftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplement=E4r:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Gesch=E4ftsf=FChrer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy