This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Dummy pthread functions in libc considered harmful
- From: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
- To: Alexander Monakov <amonakov at ispras dot ru>
- Cc: Rich Felker <dalias at libc dot org>, OndÅej BÃlka <neleai at seznam dot cz>, Andreas Schwab <schwab at suse dot de>, libc-alpha at sourceware dot org
- Date: Mon, 31 Aug 2015 16:58:02 +0200
- Subject: Re: Dummy pthread functions in libc considered harmful
- Authentication-results: sourceware.org; auth=none
- References: <mvmr3ms4sbj dot fsf at hawking dot suse dot de> <20150824153816 dot GC3210 at type dot bordeaux dot inria dot fr> <20150824162250 dot GD32742 at brightrain dot aerifal dot cx> <20150825125035 dot GA3463 at domone> <alpine dot LNX dot 2 dot 20 dot 1508251557030 dot 18864 at monopod dot intra dot ispras dot ru> <20150825143615 dot GH32742 at brightrain dot aerifal dot cx> <alpine dot LNX dot 2 dot 20 dot 1508311747010 dot 4709 at monopod dot intra dot ispras dot ru>
Alexander Monakov, le Mon 31 Aug 2015 17:54:46 +0300, a écrit :
> As a result, a libc "stub" mutex must:
>
> - contain a full implementation for process-shared mutexes
> - for non-shared mutexes in single-threaded processes, modify them
> consistently with non-stub implementation (but modifications need not be
> atomic)
>
> Does Glibc do the former? (the bug report is about Glibc not doing the latter)
See nptl/forward.c: all Glibc does in those hooks is to return 0.
Samuel