From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43757-done@debbugs.gnu.org, jonathan.brielmaier@web.de
Subject: bug#43757: cuirass: Fail to fetch "guix" input.
Date: Sat, 03 Oct 2020 14:00:42 +0200 [thread overview]
Message-ID: <87k0w7frit.fsf@gnu.org> (raw)
In-Reply-To: <87h7rbisa6.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 03 Oct 2020 11:16:01 +0200")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> ERROR: In procedure make-stack:
>> Attempt to suspend fiber within continuation barrier
>
> Turns out "par-map" call does not seem suspendable, even though I'm not
> sure why. Maybe Ludo can help here :) ?
‘par-map’ is implemented in terms of futures, and futures use their own
thread pool. What’s likely to block is ‘touch’: it essentially waits on
a condition variable, which Fibers cannot interrupt.
I’d say that mixing fibers and ‘par-map’ is a bad idea. :-)
If we need such a thing, I think we should implement it on top of
Fibers. Implementing futures on top of fibers + channels should be
easier than what (ice-9 futures) does.
> This is fixed with: 761443bca6178b4ac299a8bd368d1cac4abda5f8.
Why not just replace ‘par-map’ with ‘map’? That sounds easier and I
suspect it doesn’t change much performance-wise.
(There’s a 2nd use of ‘par-map’ in that file.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-03 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:55 bug#43757: cuirass: Fail to fetch "guix" input Mathieu Othacehe
2020-10-03 9:16 ` Mathieu Othacehe
2020-10-03 12:00 ` Ludovic Courtès [this message]
2020-10-03 13:14 ` Mathieu Othacehe
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0w7frit.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43757-done@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=othacehe@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).