unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org
Subject: Re: posix/native thread status?
Date: 09 Jun 2003 22:32:02 +0200	[thread overview]
Message-ID: <87d6hn9em5.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87add07jtk.fsf@pooh-sticks-bridge.tapsellferrier.co.uk>

Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:

> I've been poking around the guile threading stuff. Am I right in
> thinking the work on native threads stopped.

No, it is merely, well, blocked.  But because of unfair work
scheduling, it is getting unblocked for quite some time.

The Guile CVS HEAD version (aka the 1.7 series) has supprt for native
POSIX threads.  While threads are in 'Guile mode', they are restricted
to cooperate their use of the global resources (such as the GC), but
they are implemented using the POSIX threading API of the underlying
platform.

> Linux threads have been made posix compliant for kernel 2.6. Would
> the issue of native threading be good to look at again?

Yes, please try the Guile 1.7 series, maybe from

  ftp://ftp.dt.e-technik.uni-dortmund.de/pub/guile/snapshots/guile-core.unstable.tar.gz

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


      reply	other threads:[~2003-06-09 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 12:19 posix/native thread status? Nic Ferrier
2003-06-09 20:32 ` Marius Vollmer [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=87d6hn9em5.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --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).