This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] [BZ #18970]: Reference of pthread_setcancelstate in libc.a
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 17 Sep 2015 15:33:41 -0700 (PDT)
- Subject: Re: [PATCH] [BZ #18970]: Reference of pthread_setcancelstate in libc.a
- Authentication-results: sourceware.org; auth=none
- References: <20150917152135 dot GA25716 at intel dot com> <20150917195803 dot E05DF2C3B40 at topped-with-meat dot com> <CAMe9rOrGYk6s94vvSVC1R7uBS-qGZaH8Pdwr62G+ZZdgnLKeig at mail dot gmail dot com> <20150917215151 dot 6201A2C3B40 at topped-with-meat dot com> <CAMe9rOrqvtyJbEiVRnfbnt25Wh-gLin=BQDWQV7owmQ6Pbu2RQ at mail dot gmail dot com>
> Does it mean it is OK for all most of, if not all, non-ANSI C functions,
> in glibc to use all POSIX.1 symbols? This is the usage of any non-ANSI C
> functions may pull in any POSIX.1 symbols.
In general I would have said that's true. But as Joseph pointed out, there
are standards we support, such as XPG4, that do not include all of recent
vintages of POSIX.1. So I'd say it's still true for things in POSIX.1-1990
(notably not including pthreads). And sometimes that's enough for it to be
completely obvious: anything outside outside ISO C can use read, write, and
close. But byeond that it quickly becomes so picayune that I think we are
better off looking at the conform/data files rather than trying to use any
easy "rules of thumb" like this.