Re: size_t and printk and Xen

[Christoph Egger <Christoph.Egger@amd.com>]

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

-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy