unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Vok Vojwo <ceving@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: ice-9 threads parallel
Date: Wed, 26 Oct 2011 20:02:45 +0200	[thread overview]
Message-ID: <871utzzl4q.fsf@pobox.com> (raw)
In-Reply-To: <CAGUt3y4C1Na4tGgBmuLN9DudtOtuUhUfJx5vkWrPyCxJOBA_gQ@mail.gmail.com> (Vok Vojwo's message of "Wed, 26 Oct 2011 17:38:44 +0200")

On Wed 26 Oct 2011 17:38, Vok Vojwo <ceving@gmail.com> writes:

> On my system current-processor-count returns 2. I use random with the
> same seed: first in normal evaluation order and second in parallel.
> But the two evaluations return the same result. I expected that the
> order of the random numbers differs but it is the same. Why?

Works for me.  Perhaps you have some future running that is taking up
one of the CPUs already?

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-10-26 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 15:38 ice-9 threads parallel Vok Vojwo
2011-10-26 18:02 ` Andy Wingo [this message]

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=871utzzl4q.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=ceving@gmail.com \
    --cc=guile-user@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).