This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Thread-, Signal- and Cancellation-safety documentation
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 26 Mar 2013 08:23:38 +0100
- Subject: Re: Thread-, Signal- and Cancellation-safety documentation
- References: <orppym7okv dot fsf at livre dot home>
On Tue, Mar 26, 2013 at 01:49:20AM -0300, Alexandre Oliva wrote:
> I've (not so) recently started working on documenting these safety
> properties of glibc functions. I believe now have enough of a patchset
> to get the discussion on form and content started.
>
snip
> @deftypefun int fesetround (int @var{round})
> +@safety{@mtsafe{FIXME: unsafe ppc-nofpu-sim}@assafe{}@acsafe{}}
> Changes the currently selected rounding mode to @var{round}. If
> @var{round} does not correspond to one of the supported rounding modes
> nothing is changed. @code{fesetround} returns zero if it changed the
Documentation does not say if state is thread local or not. C11 says it
should be thread local. Could we document it is always thread local or
are incompatible implementations in the wild?