This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: Change pid_t base type
- From: Eric Blake <eblake at redhat dot com>
- To: Joel Sherrill <joel dot sherrill at gmail dot com>, Henri Chataing <henri dot chataing at provenrun dot com>
- Cc: Newlib <newlib at sourceware dot org>
- Date: Wed, 1 Aug 2018 09:33:47 -0500
- Subject: Re: Change pid_t base type
- References: <040f00d1-fff3-adf7-4288-02dc1e2d9e3d@provenrun.com> <CAF9ehCUkdU8Wasm3uLQzbADOO2-vsahuX2Z=wpBbfJ0Jsp7Sxg@mail.gmail.com>
On 08/01/2018 09:22 AM, Joel Sherrill wrote:
http://pubs.opengroup.org/onlinepubs/009696699/basedefs/sys/types.h.html
Says pid_t can be no larger than long if I am reading that correctly.
"The implementation shall support one or more programming environments
in which the widths of blksize_t, pid_t, size_t, ssize_t, suseconds_t,
and useconds_t are no greater than the width of type long. The names of
these programming environments can be obtained using the confstr()
function or the getconf utility."
Is POSIX a concern? Or is long 64-bits on all your targets?
If long is 32 bits, do you support two separate compilation environments
(one for POSIX with 32-bit pid_t, the other for full 64-bit pid_t)?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org