From: Maxime Devos <maximedevos@telenet.be>
To: 46230@debbugs.gnu.org
Subject: bug#46230: When are spurious wakeups of condition variables possible?
Date: Mon, 01 Feb 2021 10:53:26 +0100 [thread overview]
Message-ID: <a6392881cf8dae78e74c5f949d26850941343156.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi guilers,
Whether spurious wakeups of condition variables are
possible isn't documented in the manual. Apparently,
guile may or may not actually prevent spurious wakeups
(#guile, Mon 1 Feb 09:19:29 UTC 2021). The bug is:
* No mention of the possibility of spurious wakeups
in the manual,
* and perhaps (idk) guile not preventing spurious
wakeups.
Even if guile stops all spurious wakeups from being
visible to Scheme code, could this be documented?
Then people don't have to worry about this anymore.
Maxime.
P.S. I'm not subscribed to bug-guile@gnu.org, please add
me to To: or CC:.
--
Maxime Devos <maximedevos@telenet.be>
PGP Key: C1F3 3EE2 0C52 8FDB 7DD7 011F 49E3 EE22 1917 25EE
Freenode handle: mdevos
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
reply other threads:[~2021-02-01 9:53 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6392881cf8dae78e74c5f949d26850941343156.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=46230@debbugs.gnu.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).