This is the mail archive of the
mailing list for the glibc project.
Re: Should pthread_kill be marked __THROW?
- From: Torvald Riegel <triegel at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Florian Weimer <fweimer at redhat dot com>
- Date: Thu, 07 Apr 2016 13:35:58 +0200
- Subject: Re: Should pthread_kill be marked __THROW?
- Authentication-results: sourceware.org; auth=none
- References: <56E70876 dot 7070109 at redhat dot com> <20160318223555 dot 091B72C3C60 at topped-with-meat dot com>
On Fri, 2016-03-18 at 15:35 -0700, Roland McGrath wrote:
> I don't really understand the rationale by which you think pthread_kill (or
> anything else) should be any sort of barrier if it isn't clearly specified
> in POSIX (or appropriate standard for something else) that it must be one.
I agree. Calling a signal handler synchronously is not a concurrency
problem in the sense of synchronization with other threads. The signal
handler can be considered concurrency, but then we should rather tell
the compiler that pthread_kill is like a raise, or not?