From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Cooperative POSIX threads?
Date: Mon, 21 Oct 2002 15:39:12 -0500 [thread overview]
Message-ID: <87r8ejbk7j.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87u1jfvlpq.fsf@zagadka.ping.de> (Marius Vollmer's message of "21 Oct 2002 17:46:25 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> I noticed that signal delivery does not really work when using coop
> threads together with the LinuxThreads compatability workaround (i.e,
> when configured --with-threads=coop and --enable-linuxthreads)
>
> While pondering what to do, I thought about the following:
>
> Let's make another thread suport option, "coop-pthreads" that will use
> pthreads for implementing threads but will rig it so that all threads
> that use Guile are executing cooperatively.
At this point, how many platforms are there that support libqthreads
and guile, but not posix threads? If there aren't any and presuming
your idea works out, could we just drop qthreads in favor of posix
threads? What would be the tradeoffs?
(I'd love to get rid of the qthread per-platform special-casing in
debian/rules.)
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-10-21 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:46 Cooperative POSIX threads? Marius Vollmer
2002-10-21 18:01 ` Mikael Djurfeldt
2002-10-21 18:47 ` Marius Vollmer
2002-10-21 19:52 ` Mikael Djurfeldt
2002-10-21 20:39 ` Rob Browning [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=87r8ejbk7j.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).