From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: tromey@redhat.com, lekktu@gmail.com, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: the state of the concurrency branch
Date: Tue, 27 Aug 2013 22:08:41 +0300 [thread overview]
Message-ID: <83fvtveyti.fsf@gnu.org> (raw)
In-Reply-To: <521CF58A.20507@cs.ucla.edu>
> Date: Tue, 27 Aug 2013 11:52:58 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: Eli Zaretskii <eliz@gnu.org>, lekktu@gmail.com,
> monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> On 08/27/13 11:46, Tom Tromey wrote:
> > What is your plan for the no-threads case?
>
> Use the gnulib pthreads module. It arranges for
> "#include <pthreads.h" to work on all platforms, with
> a no-op implementation for platforms that don't support
> pthreads. It's similar to what is in systhread.h now,
> except it doesn't impose an extra naming layer.
I'd like to be at liberty to implement the few threads calls needed
for Emacs in a way that doesn't use pthreads ported to Windows. Pth
doesn't seem to support Windows (and the latest release was in 2006,
not an encouraging sign).
Gnulib pthreads is OK for a no-op implementation, but that's not what
I have in mind.
Please make the changes to the current code keeping in mind a separate
non-pthread implementation for MS-Windows. (I'm okay with adding a
separate file, say w32thread.c, which would emulate pthread calls, if
that's the model we want to follow exclusively. Alternatively, we
could have a separate HAVE_PTHREADS and HAVE_W32THREADS branches of
the same few low-level functions.)
next prev parent reply other threads:[~2013-08-27 19:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 19:26 the state of the concurrency branch Tom Tromey
2013-08-25 19:36 ` Paul Eggert
2013-08-25 19:43 ` Tom Tromey
2013-08-25 20:02 ` Paul Eggert
2013-08-26 14:55 ` Tom Tromey
2013-08-25 20:30 ` Tom Tromey
2013-08-26 16:48 ` Stefan Monnier
2013-08-26 17:04 ` Juanma Barranquero
2013-08-26 17:19 ` Tom Tromey
2013-08-26 18:51 ` Eli Zaretskii
2013-08-26 21:29 ` Stefan Monnier
2013-08-27 2:30 ` Tom Tromey
2013-08-27 16:08 ` Eli Zaretskii
2013-08-27 18:05 ` Paul Eggert
2013-08-27 18:23 ` Tom Tromey
2013-08-27 18:39 ` Paul Eggert
2013-08-27 18:46 ` Tom Tromey
2013-08-27 18:52 ` Paul Eggert
2013-08-27 19:08 ` Eli Zaretskii [this message]
2013-08-27 19:12 ` Paul Eggert
2013-08-27 18:26 ` Eli Zaretskii
2013-08-27 19:14 ` Tom Tromey
2013-08-27 19:24 ` Eli Zaretskii
2013-08-27 19:29 ` Tom Tromey
2013-08-28 0:50 ` Stefan Monnier
2013-08-28 4:16 ` Eli Zaretskii
2013-08-28 4:31 ` Tom Tromey
2013-08-28 4:58 ` Eli Zaretskii
2013-08-28 13:21 ` Stefan Monnier
2013-08-28 13:48 ` Tom Tromey
2013-08-28 14:27 ` Stefan Monnier
2013-08-28 16:23 ` Eli Zaretskii
2013-08-29 3:54 ` Tom Tromey
2013-08-29 15:10 ` Eli Zaretskii
2013-08-31 9:57 ` Eli Zaretskii
2013-08-31 11:51 ` Eli Zaretskii
2013-08-31 13:42 ` Eli Zaretskii
2013-09-01 15:49 ` Eli Zaretskii
2013-09-02 15:27 ` Eli Zaretskii
2013-08-28 0:45 ` Stefan Monnier
2013-08-28 2:34 ` Tom Tromey
2013-08-27 18:33 ` Tom Tromey
2013-08-28 15:58 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 18:24 Barry OReilly
2013-10-16 20:25 ` Barry OReilly
2013-10-18 1:41 ` Tom Tromey
2013-10-18 3:32 ` Tom Tromey
2013-10-18 18:13 ` Stefan Monnier
2013-10-18 18:16 ` Tom Tromey
2013-10-19 18:41 ` Richard Stallman
2013-10-19 19:29 ` Barry OReilly
2013-10-19 21:42 ` Stefan Monnier
2013-10-20 0:41 ` Barry OReilly
2013-10-21 15:08 ` Tom Tromey
2013-10-21 16:07 ` Barry OReilly
2013-10-21 18:17 ` Stefan Monnier
2013-10-21 16:41 ` Stefan Monnier
2013-10-19 20:21 ` Barry OReilly
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=83fvtveyti.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=tromey@redhat.com \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.