This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [MTASCsft PATCH 03/??] MT-, AS- and AC-Safety docs: manual/arith.texi
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: codonell at redhat dot com, libc-alpha at sourceware dot org
- Date: Wed, 29 Jan 2014 01:14:12 -0500
- Subject: Re: [MTASCsft PATCH 03/??] MT-, AS- and AC-Safety docs: manual/arith.texi
- Authentication-results: sourceware.org; auth=none
- References: <ortxelb5zd dot fsf at livre dot home> <or4n4uoncj dot fsf at livre dot home> <orr47yn3kl dot fsf_-_ at livre dot home> <52E89459 dot 1080105 at redhat dot com> <or61p3cotj dot fsf at livre dot home>
On 01/29/2014 12:57 AM, Alexandre Oliva wrote:
> On Jan 29, 2014, "Carlos O'Donell" <carlos@redhat.com> wrote:
>
>> On 01/23/2014 10:03 AM, Alexandre Oliva wrote:
>
>>> @deftypefun int feclearexcept (int @var{excepts})
>>> +@safety{@prelim{}@mtsafe{}@assafe{@assposix{}}@acsafe{@acsposix{}}}
>
>> It's not one of the 3 posix AC-safe functions.
>
>> How is this @acsposix{}?
>
> POSIX has it's not AC-Safe; our implementation it is, therefore it's
> unlike POSIX, thus !posix. It's within @acsafe{}, thus the correct note
> is @acsposix{}.
Sorry, you're right.
>> It's not one of the set of AS-safe functions in POSIX.
>
>> How is this @assposix{}?
>
> Same reasoning. POSIX says it's AS-Unsafe, our implementation is
> AS-Safe, thus !posix.
>
Thanks.
Looks good then.
Cheers,
Carlos.