This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: AW: Specific Linux syscalls for glibc API
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: "Warlich, Christof" <christof dot warlich at siemens dot com>, Joseph Myers <joseph at codesourcery dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Wed, 18 Nov 2015 16:07:26 +0000
- Subject: Re: AW: Specific Linux syscalls for glibc API
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1511171606330 dot 14808 at digraph dot polyomino dot org dot uk> <6D83E89737156549AEA25EF9ED712C5D168D31 at DEFTHW99EK1MSX dot ww902 dot siemens dot net>
On 18/11/15 12:57, Warlich, Christof wrote:
On 11/17/2015 05:34 PM, Joseph Myers wrote
* gettid, pthread_gettid_np (bug 6399).
I'm not sure w.r.t. the added value of a gettid wrapper though: Assuming the
availability of pthread_gettid_np(), pthread_gettid_np(pthread_self()) would
(apart from some locking to prevent thread termination in the meantime) just
do what gettid() is supposed to do.
i don't see why would you lock there.
(this api should be as-safe)
pthread_gettid_np is problematic api because of the
issue Florian raised (tid is lost after a thread
exited but not yet joined and that should not be
visible to the caller, so this api is only possible
to implement if tid handling is redesigned).