Thread-, Signal- and Cancellation-safety documentation

Ondřej Bílka neleai@seznam.cz
Tue Mar 26 07:28:00 GMT 2013


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?




More information about the Libc-alpha mailing list