From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Thomas Klausner <tk@giga.or.at>
Subject: Re: tzalloc (was: Re: parse-datetime test failure on NetBSD)
Date: Sun, 14 Mar 2021 12:02:10 -0700 [thread overview]
Message-ID: <d2f3dd24-5a9b-593a-d394-d9f75332061e@cs.ucla.edu> (raw)
In-Reply-To: <4335650.5adnljZN5I@omega>
On 3/14/21 11:33 AM, Bruno Haible wrote:
> A close term is "multithread-safe". The API could be implemented in a
> multithread-safe way, but time_rz.c is not multithread-safe, due to the
> function 'change_env'.
>
> It is planned to provide a multithread-safe implementation at some point?
My plan has been to add them eventually to glibc, where they would be
multithread-safe. It'd be nice to also make them multithread-safe in
Gnulib, so long as that doesn't make them harder to use with existing
apps, all of which currently use these functions only in a single thread
(which is why this is low priority). The only platform I know that
currently has them is NetBSD, where I believe they're multithread-safe.
I took the word "reentrant" from the "_r" suffix, which as you note is a
bit of a misnomer here (though a widely used misnomer...).
next prev parent reply other threads:[~2021-03-14 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 8:24 parse-datetime test failure on NetBSD Thomas Klausner
2021-03-14 10:42 ` Bruno Haible
2021-03-14 11:05 ` Thomas Klausner
2021-03-14 11:53 ` tzalloc (was: Re: parse-datetime test failure on NetBSD) Bruno Haible
2021-03-14 16:02 ` Paul Eggert
2021-03-14 18:33 ` Bruno Haible
2021-03-14 19:02 ` Paul Eggert [this message]
2021-03-14 19:37 ` tzalloc Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2f3dd24-5a9b-593a-d394-d9f75332061e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=tk@giga.or.at \
/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).