From: Joel Sherrill <joel.sherrill@gmail.com>
To: Newlib <newlib@sourceware.org>
Subject: C11/POSIX-2024 Questions
Date: Fri, 28 Jun 2024 09:37:07 -0500 [thread overview]
Message-ID: <CAF9ehCVyevWK5GaGrPAz713rnpZnXFHaXedcu=0eAu-98RbsLg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi
I am finishing up reviewing the additions from POSIX Issue 8 which was
released recently. I noticed a few things and have questions on the right
approach.
+ I only have the final draft for POSIX-2024. It says "_POSIX_VERSION to
the value
20yymmL." It isn't on the web yet for the HTML version. Anyone know the
value this has in the final version?
+ sys/features.h appears to need this new POSIX version added at least to
the comment block. I don't think it necessarily changes any logic below
that.
+ memmem is in string.h under the __GNU_VISIBLE guard. Does it now need to
be under a __POSIX_VISIBLE > 2024mmdd and __GNU_VISIBLE?
+ aligned_alloc in stdlib.h is only guarded by C > 2011. Does that need to
be an || POSIX >= 2024 also?
+ C11 and POSIX-2024 add these complex methods.
double complex CMPLX(double x, double y);
float complex CMPLXF(float x, float y);
long double complex CMPLXL(long double x, long double y);
FreeBSD has a macro implementation (
https://github.com/lattera/freebsd/blob/master/include/complex.h#L49). If I
add that to complex.h, does it also need a __ISO_C_VISIBLE >= 2011 ||
__POSIX_VISIBLE > 2024mmdd guard?
+ Should I continue to look for guards on things that are newly added in
POSIX 2024 and already in newlib?
That's it so far. Just picky stuff that I plan to address given some advice.
--joel
next reply other threads:[~2024-06-28 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 14:37 Joel Sherrill [this message]
2024-06-28 16:00 ` John Scott
2024-06-28 21:32 ` brian.inglis
2024-06-28 22:01 ` Joel Sherrill
2024-06-28 22:32 ` brian.inglis
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='CAF9ehCVyevWK5GaGrPAz713rnpZnXFHaXedcu=0eAu-98RbsLg@mail.gmail.com' \
--to=joel.sherrill@gmail.com \
--cc=newlib@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).