This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- From: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>
- Date: Thu, 18 Jul 2013 11:44:11 +0200
- Subject: Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- References: <51E42BFE dot 7000301 at redhat dot com> <20130718093506 dot GH5942 at type dot bordeaux dot inria dot fr> <51E7B841 dot 9010805 at redhat dot com>
Carlos O'Donell, le Thu 18 Jul 2013 05:41:21 -0400, a écrit :
> On 07/18/2013 05:35 AM, Samuel Thibault wrote:
> > BTW, changing CPU_SETSIZE does not change glibc's ABI: it is only used
> > in inlines in headers, never in the glibc source code.
> >
> > It may however change ABIs of other libraries if they happen to have
> > put it into their ABI (e.g. expose an explicitly CPU_SETSIZE-lengthed
> > bitmap)
>
> For all intents and purposes it is part of glibc's public ABI,
How so?
Samuel