public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
	 Joseph Myers <joseph@codesourcery.com>,
	Jens Gustedt <jens.gustedt@inria.fr>,
	 GNU libc <libc-alpha@sourceware.org>,  enh <enh@google.com>
Subject: Re: [PATCH v2 4/4] c2y: Add function cnd_timedwait_base and mtx_timedlock_base
Date: Wed, 21 Jun 2023 12:40:45 +0200	[thread overview]
Message-ID: <878rcd5c9e.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAE2XoE8S3ajnDYa+EANH_EBPFDkq84QELbJYqvrztL+Vc_14QQ@mail.gmail.com> (=?utf-8?B?Iue9l+WLh+WImihZb25nZ2FuZw==?= Luo)"'s message of "Wed, 21 Jun 2023 18:16:14 +0800")

* 罗勇刚(Yonggang Luo):

> its not submit to wg14 yet, because this is not a totally new feature,
> I need to implement it first to see if it's possible, and this is
> chicken/egg problem, so I decided implement it first to receiving
> feedback, and after minimal agreement received, I would submit
> proposal to wg14 if am qualified.

You need to take this up with WG14.  This is not the right list for
that.

There is no reason to duplicate existing POSIX functionality or
extensions in glibc just because they might be included in a future
version of the C standard.  Usually, WG14 does not adopt actually
deployed interfaces, but makes up new ones (despite the “no invention,
without exception“ still in the charter).  In that case, we end up with
three incompatible interfaces, the POSIX one, our C prototype, and the
actual C interface.

Thanks,
Florian


  parent reply	other threads:[~2023-06-21 10:40 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 17:17 [PATCH v2 0/4] c2y proposal add monotonicwait support for mtx and ctx Yonggang Luo
2023-06-20 17:17 ` [PATCH v2 1/4] clang-format: should format with 2 space and do not usage tab Yonggang Luo
2023-06-20 17:45   ` Zack Weinberg
2023-06-21  6:31     ` 罗勇刚(Yonggang Luo)
2023-06-21  6:47       ` Xi Ruoyao
2023-06-21  6:55         ` 罗勇刚(Yonggang Luo)
2023-06-21  7:13           ` Xi Ruoyao
2023-06-21  7:36             ` 罗勇刚(Yonggang Luo)
2023-06-21 14:26       ` Zack Weinberg
2023-06-21  7:17     ` Xi Ruoyao
2023-06-21 16:19     ` Carlos O'Donell
2023-06-21 17:35       ` Joseph Myers
2023-06-21 17:41         ` 罗勇刚(Yonggang Luo)
2023-06-21 17:49           ` Andrew Pinski
2023-06-21 17:59             ` 罗勇刚(Yonggang Luo)
2023-06-21 18:31               ` Arsen Arsenović
2023-06-21 18:42                 ` 罗勇刚(Yonggang Luo)
2023-06-21 19:36           ` Zack Weinberg
2023-06-21 21:26         ` Paul Eggert
2023-06-22 21:43           ` Joseph Myers
2023-06-22 21:48             ` Paul Eggert
2023-06-20 17:17 ` [PATCH v2 2/4] time: Implement c23 timespec_get base Yonggang Luo
2023-06-20 20:37   ` Joseph Myers
2023-06-21  6:42     ` 罗勇刚(Yonggang Luo)
2023-06-20 17:17 ` [PATCH v2 3/4] c11: Switch to use pthread_mutex_clocklock and pthread_cond_clockwait to implement cnd and mtx lock and wait Yonggang Luo
2023-06-20 17:17 ` [PATCH v2 4/4] c2y: Add function cnd_timedwait_base and mtx_timedlock_base Yonggang Luo
2023-06-20 20:41   ` Joseph Myers
2023-06-21  9:21     ` 罗勇刚(Yonggang Luo)
2023-06-21  9:54       ` Xi Ruoyao
2023-06-21 10:16         ` 罗勇刚(Yonggang Luo)
2023-06-21 10:25           ` Xi Ruoyao
2023-06-21 10:40           ` Florian Weimer [this message]
2023-06-21 13:23             ` Jₑₙₛ Gustedt
2023-06-21 12:09       ` Joseph Myers
2023-06-21 14:30       ` enh
2023-06-21 15:08         ` Joseph Myers
2023-06-21 18:39         ` 罗勇刚(Yonggang Luo)
2023-06-21 19:04           ` enh
2023-06-21 19:07             ` 罗勇刚(Yonggang Luo)
2023-06-21 19:18               ` enh
2023-06-21 19:38                 ` 罗勇刚(Yonggang Luo)
2023-06-21 19:41                   ` enh
2023-06-21 20:14                     ` 罗勇刚(Yonggang Luo)
2023-06-21 19:43                 ` 罗勇刚(Yonggang Luo)
2023-06-20 20:50   ` Joseph Myers
2023-06-20 20:45 ` [PATCH v2 0/4] c2y proposal add monotonicwait support for mtx and ctx Joseph Myers
2023-06-21  6:52   ` 罗勇刚(Yonggang Luo)
2023-06-21  7:14     ` Xi Ruoyao

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=878rcd5c9e.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=enh@google.com \
    --cc=jens.gustedt@inria.fr \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=luoyonggang@gmail.com \
    --cc=xry111@xry111.site \
    /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).