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: Joseph Myers <joseph at codesourcery dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Roland McGrath <roland at hack dot frob dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 17 Sep 2015 22:33:01 +0000
- 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>
On Thu, 17 Sep 2015, H.J. Lu wrote:
> On Thu, Sep 17, 2015 at 2:51 PM, Roland McGrath <roland@hack.frob.com> wrote:
> >> Is this a valid test?
> >
> > No. There should be no need for individual tests like that. The
> > linknamespace tests should catch such things if the conform data is correct
> > (and if it's not, the right thing is to fix the conform data).
> >
> > AFAIK fmtmsg is only specified in standards that put all POSIX.1 symbols
> > (including pthread_setcancelstate) in the implementation name space.
>
> 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.
Although most supported feature test macros in glibc are supersets of
POSIX.1:1990, it's also the case that ISO C functions use lots of
non-ISO-C functions via their implementation-namespace __* names - if an
ISO C function uses __foo (strong name to which weak foo is a POSIX.1
alias) then __foo can't use bar (non-ISO-C function) although it can use
__bar.
--
Joseph S. Myers
joseph@codesourcery.com