From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27476@debbugs.gnu.org
Subject: bug#27476: libguile/memoize.c is not thread safe, so syntax parameter expansion is not thread-safe
Date: Wed, 09 May 2018 12:18:01 +0200 [thread overview]
Message-ID: <87lgct5e06.fsf@igalia.com> (raw)
In-Reply-To: <878t8tyyfk.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 09 May 2018 11:23:59 +0200")
On Wed 09 May 2018 11:23, ludo@gnu.org (Ludovic Courtès) writes:
>> Is the memoization you are referring to the "set!" in the "lazy" form in
>> ice-9/eval.scm ? Or something else? FWIW I would not think the "set!"
>> could be the issue, at least on x86, but who knows.
>
> Actually I’m not sure exactly. ‘memoize-expression’ itself is
> side-effect-free, right?
As far as I know (and I had a look this morning), yes. It takes a
Tree-IL input and returns a memoized output. The internal mutation that
exists in the evaluator is just the lazy "compilation" (see the
invocations of the "lazy" form).
Of course the function being evaluated could mutate shared state as
well!
Andy
next prev parent reply other threads:[~2018-05-09 10:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:38 guix pull fails on powerful server Ricardo Wurmus
2017-09-22 14:10 ` bug#27476: " Ludovic Courtès
2017-09-25 7:27 ` Andy Wingo
2017-09-25 13:03 ` Ludovic Courtès
2017-09-25 13:03 ` Ludovic Courtès
2017-09-25 14:02 ` bug#27476: " Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
2017-10-03 20:29 ` bug#27476: " Marius Bakke
2017-10-03 20:29 ` Marius Bakke
2017-10-04 13:15 ` bug#27476: " Ricardo Wurmus
2017-10-04 13:15 ` Ricardo Wurmus
2017-10-04 15:09 ` bug#27476: " Clément Lassieur
2017-10-04 15:09 ` Clément Lassieur
2017-10-04 16:17 ` bug#27476: " Ricardo Wurmus
2017-10-07 15:11 ` Ludovic Courtès
2017-10-10 7:17 ` bug#27476: " Ricardo Wurmus
2017-10-10 7:17 ` Ricardo Wurmus
2017-10-10 11:32 ` bug#27476: " Ludovic Courtès
2017-10-10 11:32 ` Ludovic Courtès
2017-10-07 15:11 ` bug#27476: " Ludovic Courtès
2017-10-12 13:37 ` Ludovic Courtès
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 21:04 ` Ricardo Wurmus
2017-10-13 21:10 ` Ricardo Wurmus
2017-10-12 13:37 ` Ludovic Courtès
2017-11-07 10:57 ` Ludovic Courtès
2017-11-07 10:57 ` Ludovic Courtès
2018-04-30 21:19 ` Ludovic Courtès
2018-04-30 21:39 ` bug#27476: libguile/memoize.c is not thread safe, so syntax parameter expansion is not thread-safe Ludovic Courtès
2018-05-09 8:41 ` Andy Wingo
2018-05-09 9:23 ` Ludovic Courtès
2018-05-09 10:18 ` Andy Wingo [this message]
2019-02-06 14:48 ` Ludovic Courtès
2019-02-06 16:14 ` Andy Wingo
2019-02-06 22:09 ` Ludovic Courtès
2019-01-29 10:07 ` bug#27476: guix pull fails on powerful server Ricardo Wurmus
2019-01-29 10:07 ` Ricardo Wurmus
2017-09-25 8:43 ` Clément Lassieur
2017-09-25 8:43 ` Clément Lassieur
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=87lgct5e06.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=27476@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.