From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Update floating-point feature test macro handling for C2X
Date: Tue, 1 Jun 2021 17:30:51 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2106011729080.634934@digraph.polyomino.org.uk> (raw)
In-Reply-To: <0fa310c0-d586-66b8-eb86-bdc554617791@linaro.org>
On Fri, 28 May 2021, Adhemerval Zanella via Libc-alpha wrote:
> > @@ -215,6 +215,13 @@ enabled. Only some of the features from this TS are supported by
> > @theglibc{}.
> > @end defvr
> >
> > +@defvr Macro __STDC_WANT_IEC_60559_EXT__
> > +@standards{ISO, (none)}
> > +If you define this macro, ISO C2X features defined in Annex F of that
> > +standard are enabled. This affects declarations of the
> > +@code{totalorder} functions and functions related to NaN payloads.
> > +@end defvr
> > +
> > @defvr Macro _GNU_SOURCE
> > @standards{GNU, (none)}
> > If you define this macro, everything is included: @w{ISO C89}, @w{ISO
>
> Should it add a note for CR_DECIMAL_DIG as well? Or the gcc documentation
> is suffice?
I think this part of the manual is only expected to cover the effects of
feature test macros on glibc's own headers, not on compiler-provided
headers.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-06-01 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 23:57 Joseph Myers
2021-05-20 22:06 ` Ping " Joseph Myers
2021-05-27 16:36 ` Ping^2 " Joseph Myers
2021-05-21 7:27 ` Florian Weimer
2021-05-24 19:08 ` Joseph Myers
2021-05-28 20:33 ` Adhemerval Zanella
2021-06-01 17:30 ` Joseph Myers [this message]
2021-06-01 17:36 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2106011729080.634934@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).