[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250321125008.GH1827@brightrain.aerifal.cx>
Date: Fri, 21 Mar 2025 08:50:08 -0400
From: Rich Felker <dalias@...c.org>
To: Jₑₙₛ Gustedt <jens.gustedt@...ia.fr>
Cc: musl@...ts.openwall.com
Subject: Re: implement pthread_cond_clockwait?
On Fri, Mar 21, 2025 at 11:05:27AM +0100, Jₑₙₛ Gustedt wrote:
> Hi,
> Posix 2024 now has this function and it is mandatory. It seems that it
> is not very difficult to implement in musl. Would it make sense to
> send a patch?
I think so, but there might already be one. IIRC there are several
other explicit-clock functions to be added. I was originally hesitant
before they were standard because it's an extra level of call that
can't be a tail-call on many archs (because extra argument), but now
it's necessary to add them anyway. If the cost matters it could
probably be alleviated with an explicit trylock first, but we already
do the equivalent for normal-type mutexes which are the main ones
whose performance matters.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
