This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Add fetestexceptflag
- From: Florian Weimer <fweimer at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Cc: stli at linux dot vnet dot ibm dot com
- Date: Mon, 29 Aug 2016 11:26:09 +0200
- Subject: Re: Add fetestexceptflag
- Authentication-results: sourceware.org; auth=none
- References: <alpine.DEB.2.20.1608261734390.30788@digraph.polyomino.org.uk>
On 08/26/2016 07:37 PM, Joseph Myers wrote:
+@comment fenv.h
+@comment ISO
+@deftypefun int fetestexceptflag (const fexcept_t *@var{flagp}, int @var{excepts})
+@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
+Test whether the exception flags indicated by the parameter
+@var{excepts} are set in the variable pointed to by @var{flagp}. If
+any of them are, a nonzero value is returned which specifies which
+exceptions are set. Otherwise the result is zero.
+@code{fetestexceptflag} is from TS 18661-1:2014.
+@end deftypefun
Seeing the @assafe{} annotation makes me wonder:
How do signal handlers and these flags interact? Are they reset upon
normal termination of the signal handler, to the state they had at the
start of the handler? What about exiting the handler with siglongjmp?
Thanks,
Florian