From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: What's the problem?
Date: Fri, 12 Dec 2003 18:55:58 -0500
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <E1AUx8Y-0004zh-Qy@fencepost.gnu.org>
References: <uhe14m1fj.fsf@mid.gehheimdienst.de>
	<E1ARacL-0004cw-CJ@fencepost.gnu.org>
	<4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu>
	<5bad69zd43.fsf@lister.roxen.com>
	<4noeuon378.fsf@lockgroove.bwh.harvard.edu>
	<x5smk0wub8.fsf@lola.goethe.zz> <m3ekvkv9p4.fsf@kfs-l.imdomain.dk>
	<4ny8tsgxy6.fsf@lockgroove.bwh.harvard.edu>
	<jwvhe0gfhv2.fsf-monnier+emacs/devel@vor.iro.umontreal.ca>
	<4nhe0ggv0u.fsf@lockgroove.bwh.harvard.edu>
	<jwv65gwfbke.fsf-monnier+emacs/devel@vor.iro.umontreal.ca>
	<4nk75bwjaf.fsf@lockgroove.bwh.harvard.edu>
	<jwvekvg5h8n.fsf-monnier+emacs/devel@vor.iro.umontreal.ca>
	<4nsmjv8d32.fsf@collins.bwh.harvard.edu>
	<lhr7zfnp40.fsf_-_@dodo.bluetail.com>
	<iluk757axq3.fsf@latte.josefsson.org> <87iskpbloe.fsf@mail.jurta.org>
	<ilud6axv68v.fsf@latte.josefsson.org>
	<buowu952su5.fsf@mcspd15.ucom.lsi.nec.co.jp>
	<iluwu952pvz.fsf@latte.josefsson.org>
	<buoptexusoj.fsf@mcspd15.uc
Reply-To: rms@gnu.org
NNTP-Posting-Host: deer.gmane.org
X-Trace: sea.gmane.org 1071273883 6634 80.91.224.253 (13 Dec 2003 00:04:43 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Sat, 13 Dec 2003 00:04:43 +0000 (UTC)
Cc: juri@jurta.org, emacs-devel@gnu.org, miles@gnu.org
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Dec 13 01:04:39 2003
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AUxGx-0003DT-00
	for <emacs-devel@deer.gmane.org>; Sat, 13 Dec 2003 01:04:39 +0100
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AUxGv-0007Bf-00
	for <emacs-devel@quimby.gnus.org>; Sat, 13 Dec 2003 01:04:37 +0100
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.24)
	id 1AUy7o-0003pD-3Z
	for emacs-devel@quimby.gnus.org; Fri, 12 Dec 2003 19:59:16 -0500
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24)
	id 1AUy7b-0003lQ-00
	for emacs-devel@gnu.org; Fri, 12 Dec 2003 19:59:03 -0500
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24)
	id 1AUy7L-0003gp-2x
	for emacs-devel@gnu.org; Fri, 12 Dec 2003 19:58:59 -0500
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.24) id 1AUy7K-0003ge-L0
	for emacs-devel@gnu.org; Fri, 12 Dec 2003 19:58:46 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24)
	id 1AUx8Y-0004zh-Qy; Fri, 12 Dec 2003 18:55:58 -0500
Original-To: Stefan Monnier <monnier@iro.umontreal.ca>
In-reply-to: <jwvptevwjli.fsf-monnier+emacs/devel@vor.iro.umontreal.ca>
	(message from Stefan Monnier on 11 Dec 2003 09:12:17 -0500)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Emacs development discussions.  <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:18662
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18662

    What we're talking about is basically multiple-stacks, context-switches
    done only from Feval (i.e. at elisp granularity so there's no concurrency
    in the C code),

The number of C functions that call Feval is rather large,
and include redisplay.  So this is not quite as easy as it might seem.

Redisplay could set a flag to prevent thread-switching.  That would
remove one large piece of the problem.  How big the problem remains
after that, I am not sure.