From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: APIs in New POSIX Edition
Date: Thu, 8 Apr 2021 13:49:26 +0200 [thread overview]
Message-ID: <YG7txmcBE3zBp8Sa@calimero.vinschen.de> (raw)
In-Reply-To: <CAF9ehCVF3Z27Kvh8Qm2HjqHyUiUnCDuKSUwUqgRbhG=__EigKQ@mail.gmail.com>
On Apr 8 06:38, Joel Sherrill wrote:
> On Thu, Apr 8, 2021, 6:19 AM Corinna Vinschen <vinschen@redhat.com> wrote:
>
> > On Apr 7 18:26, Joel Sherrill wrote:
> > > Hi
> > >
> > > https://www.opengroup.org/austin/docs/austin_1110.pdf includes a set of
> > new
> > > methods to be added to the POSIX standard. RTEMS has a potential GSoC
> > > student interested in working down the list for RTEMS. Some of these make
> > > sense to be implemented in newlib. All will end up being prototyped in
> > > newlib headers somewhere.
> > >
> > > >From the document and the formatting is completely lost.
> > >
> > > The additional APIs proposed by participants in the Austin Group that
> > The
> > > Open Group has agreed to sponsor are as follows:
> >
> > > getentropy()
> > > memmem()
> > > reallocarray()
> > > strlcat()
> > > strlcpy()
> > > wcslcat()
> > > wcslcpy()
> >
> > Already in newlib.
> >
> > > ppoll()
> >
> > Already defined in Cygwin. We don't have a generic poll.h header in
> > newlib.
> >
> > > dladdr()
> >
> > Already defined in Cygwin. We don't have a generic dlfcn.h header in
> > newlib. It's questionable if this really belongs in newlib.
> >
> > > getlocalename_l()
> > > posix_getdents()
> > > sig2str()
> > > str2sig()
> >
> > No worries as soon as the API is stable.
> >
> > > pthread_cond_clockwait()
> > > pthread_mutex_clocklock()
> > > pthread_rwlock_clockrdlock()
> > > pthread_rwlock_clockwrlock()
> > > qsort_r()
> > > sem_clockwait()
> >
> > No worries, these APIs won't change compared to their already
> > existing implementations in GLibc.
> >
>
> Great.
>
> What feature guard should these be behind? Will it change for the ones
> already in place?
There will be a matching POSIX.1-2021 or so, given by date/month,
with guards along the lines of _POSIX_C_SOURCE >= 202107L.
APIS we already have should keep their current guard or'ed with
the above _POSIX_C_SOURCE test.
APIs we already have but have no guard should get _DEFAULT_SOURCE
or'ed with the above _POSIX_C_SOURCE test.
Yaakov? Does that make sense?
Thanks,
Corinna
next prev parent reply other threads:[~2021-04-08 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 23:26 Joel Sherrill
2021-04-08 11:18 ` Corinna Vinschen
2021-04-08 11:38 ` Joel Sherrill
2021-04-08 11:49 ` Corinna Vinschen [this message]
2021-04-08 11:56 ` Corinna Vinschen
2021-04-08 12:07 ` Corinna Vinschen
2021-04-09 17:55 ` Yaakov Selkowitz
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=YG7txmcBE3zBp8Sa@calimero.vinschen.de \
--to=vinschen@redhat.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).