From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: Helping with MPS Date: Wed, 21 Aug 2024 08:31:50 +0200 Message-ID: <87frqy5quh.fsf@gmail.com> References: <877ccbb3a9.fsf@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24819"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Gerd =?utf-8?Q?M=C3=B6llmann?= , emacs-devel@gnu.org, Jonathon McKitrick To: Pip Cet Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 21 08:32:29 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sgetQ-0006Gl-Sj for ged-emacs-devel@m.gmane-mx.org; Wed, 21 Aug 2024 08:32:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sgesu-0001HT-TY; Wed, 21 Aug 2024 02:31:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sgess-0001HF-IU for emacs-devel@gnu.org; Wed, 21 Aug 2024 02:31:54 -0400 Original-Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sgesq-0004h7-UX for emacs-devel@gnu.org; Wed, 21 Aug 2024 02:31:54 -0400 Original-Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-a8643a6bd55so221499866b.3 for ; Tue, 20 Aug 2024 23:31:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724221911; x=1724826711; darn=gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=3eVkyXkh7OLZQDwVE8w8jKxpeIi/NKKDEe6IUXWXIiY=; b=bItQewspOrn5dLg9/x2yekLHbw1cpGOCcJ+N0Q3IE2Pil0E79VU7sZXl4J9SqERUi+ rsY8WG10bwLinsKUThFjACvaCUMx+qJEF3xhx9NzAfH3QNnEreqME5ydQTic1g+BDUFv NG86DFPBF0bmWXj5kdiURZo5pc0gPaCmrL+02lVySKcPgV4ywOZBqMFjBqb5NOdRY2cS z+jj+H6ZYbAZaI5Sc6WGASWxh4E2Z7h/0SLJBIhpOeIoKkg4dGioRErUZ26eS1dpHG71 mjWMcosEgMlmFFshLMvQLTcuJWumbmrgQ9SRImzLYPlJUaeDWrhP2OtaTjIXBiyzYDn7 TJJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724221911; x=1724826711; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3eVkyXkh7OLZQDwVE8w8jKxpeIi/NKKDEe6IUXWXIiY=; b=O+64ummcJdTMXFUjsN0vHbSy+ubkj3tN0zi9gNgptv8MHRJxpBDfWIxq9+KmZcuj8x +BSeG0k9F0xkRebuUcnbay17VXg8CfQXXuM++9s12zWb0cqvLFrY10JoaykYo9r2IB2W ly0bv7SuqRhYEPjTbkPFr9QxNPxE9PFkbg4+vJw7eyH4HdWeq5rCgT0Pp2DI8ptz7uY4 Z38eTIw1sPRIXUopaFoF8DMrG9Kx5TaXZ6tsmJcIfNJ8wfiogq5L3hW8W4OVZDrqfiDQ UZhX70EYd+dbQSwl47jT808z2F99u7UeWN5S14eYWvXj9JuriPQIjAfG7ur8cdrSnIJz AorA== X-Forwarded-Encrypted: i=1; AJvYcCWMpzHowh4zo7FBu0Sos4PUSKgrSQfpCZzErV8CdMIUmyC0kL4FlwWHMAF+JyH8oJKBDJB1xQKN8f+fbA==@gnu.org X-Gm-Message-State: AOJu0YxNBGeTveTkJSU7cArQrNQBLkqRt2lowvyl4iljXszJf7IQu4v6 opkSdAFLW84BoZEstb7pUPi3IjRZjG5qzQWQkfqIkMRLVoSGs1vOvB9jOA== X-Google-Smtp-Source: AGHT+IEz2/H60Xe/bZAQMJXTL3q1/9jv4QxnuRDA7tfH2sL7T54AJ/QsZilmSJHCad0YlJWdJ5Eovw== X-Received: by 2002:a17:907:1c85:b0:a7a:a4be:2f95 with SMTP id a640c23a62f3a-a866f10ccf6mr88461866b.5.1724221911075; Tue, 20 Aug 2024 23:31:51 -0700 (PDT) Original-Received: from caladan (dial-181089.pool.broadband44.net. [212.46.181.89]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a83839355f5sm852603066b.106.2024.08.20.23.31.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Aug 2024 23:31:50 -0700 (PDT) In-Reply-To: <877ccbb3a9.fsf@protonmail.com> (Pip Cet's message of "Tue, 20 Aug 2024 15:52:01 +0000") Received-SPF: pass client-ip=2a00:1450:4864:20::632; envelope-from=eller.helmut@gmail.com; helo=mail-ej1-x632.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322988 Archived-At: On Tue, Aug 20 2024, Pip Cet wrote: > My current workaround is to have a flag for each signal, plus a global > flag, and set them when the signal arrives at an inopportune time. We > check them when we know we just left MPS code, and that part usually > works, but sometimes we miss the exit, and then we have to wait until > the next 'maybe_quit' to handle the signal, and that strikes me as > potentially too long a delay. > > So, if you're using GNU/Linux machines, you might run into crashes we > already know about. I can provide a temporary fix, but it doesn't feel > quite good enough for scratch/igc yet. > > Any comments or advice would be welcome, of course. What would you think about creating fork of MPS (on GitHub) that includes: a) fixes for known problems: https://github.com/Ravenbrook/mps/issues/285 https://github.com/Ravenbrook/mps/pull/257 https://github.com/Ravenbrook/mps/pull/38 https://github.com/Ravenbrook/mps/pull/83 b) removes the instruction emulation on protection faults in the AWL pool. For us, this adds a lot of complexity with questionable gains: The weak hash tables implementation is, well, complicated and for the marker-vector it's ineffective because there we use tagged pointers (apparently without problems). c) blocks signals. Not my preferred solution, but some people seem to think that that is the emacsy way to do things. ?