public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin] Cygwin: clarify importance of new GNU-specifc API
Date: Mon,  2 Aug 2021 11:57:20 +0000 (GMT)	[thread overview]
Message-ID: <20210802115720.616243858404@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=cf9a51371cdf4cfb13f40cd2d7e5916bb4c499b4

commit cf9a51371cdf4cfb13f40cd2d7e5916bb4c499b4
Author: Corinna Vinschen <corinna@vinschen.de>
Date:   Mon Aug 2 13:53:38 2021 +0200

    Cygwin: clarify importance of new GNU-specifc API
    
    Signed-off-by: Corinna Vinschen <corinna@vinschen.de>

Diff:
---
 winsup/cygwin/release/3.3.0 | 5 +++--
 winsup/doc/new-features.xml | 5 +++--
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/winsup/cygwin/release/3.3.0 b/winsup/cygwin/release/3.3.0
index bbedff45f..937e92643 100644
--- a/winsup/cygwin/release/3.3.0
+++ b/winsup/cygwin/release/3.3.0
@@ -8,8 +8,9 @@ What's new:
   of any "gmon.out" file created by profiler, ssp, or use of the gcc/g++
   option '-pg'.  (Continue using gprof to get symbolic profile displays.)
 
-- New GNU-specific APIs: pthread_cond_clockwait, pthread_mutex_clocklock,
-  pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock, sem_clockwait.
+- New GNU-specific APIs, slated to become part of the next POSIX standard:
+  pthread_cond_clockwait, pthread_mutex_clocklock, pthread_rwlock_clockrdlock,
+  pthread_rwlock_clockwrlock, sem_clockwait.
 
 
 What changed:
diff --git a/winsup/doc/new-features.xml b/winsup/doc/new-features.xml
index 74e42167a..99cb342f7 100644
--- a/winsup/doc/new-features.xml
+++ b/winsup/doc/new-features.xml
@@ -20,8 +20,9 @@ option '-pg'.  (Continue using gprof to get symbolic profile displays.)
 </para></listitem>
 
 <listitem><para>
-New GNU-specific APIs: pthread_cond_clockwait, pthread_mutex_clocklock,
-pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock, sem_clockwait.
+New GNU-specific APIs, slated to become part of the next POSIX standard:
+pthread_cond_clockwait, pthread_mutex_clocklock, pthread_rwlock_clockrdlock,
+pthread_rwlock_clockwrlock, sem_clockwait.
 </para></listitem>
 
 <listitem><para>


                 reply	other threads:[~2021-08-02 11:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210802115720.616243858404@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=cygwin-cvs@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).