From: Helmut Eller <eller.helmut@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
emacs-devel@gnu.org, "Jonathon McKitrick" <jcm@SDF.ORG>
Subject: Re: Helping with MPS
Date: Wed, 21 Aug 2024 08:31:50 +0200 [thread overview]
Message-ID: <87frqy5quh.fsf@gmail.com> (raw)
In-Reply-To: <877ccbb3a9.fsf@protonmail.com> (Pip Cet's message of "Tue, 20 Aug 2024 15:52:01 +0000")
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.
?
next prev parent reply other threads:[~2024-08-21 6:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 15:37 Helping with MPS Jonathon McKitrick via Emacs development discussions.
2024-08-20 15:52 ` Pip Cet
2024-08-20 20:41 ` Jonathon McKitrick via Emacs development discussions.
2024-08-20 20:44 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 6:31 ` Helmut Eller [this message]
2024-08-21 6:56 ` Gerd Möllmann
2024-08-21 8:02 ` Pip Cet
2024-08-21 9:23 ` Helmut Eller
2024-08-21 13:53 ` Eli Zaretskii
2024-08-21 14:36 ` Helmut Eller
2024-08-21 14:44 ` Eli Zaretskii
2024-08-21 15:10 ` Helmut Eller
2024-08-21 15:34 ` Eli Zaretskii
2024-08-21 17:44 ` Helmut Eller
2024-08-21 18:06 ` Eli Zaretskii
2024-08-20 16:05 ` Helmut Eller
2024-08-20 21:42 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 3:46 ` Gerd Möllmann
2024-08-21 5:59 ` Helmut Eller
2024-08-21 6:28 ` Arash Esbati
2024-08-21 6:54 ` Gerd Möllmann
2024-08-21 14:10 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 14:48 ` Gerd Möllmann
2024-08-21 15:08 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 15:40 ` Gerd Möllmann
2024-08-21 15:46 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 16:23 ` Gerd Möllmann
2024-08-21 18:00 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:04 ` Gerd Möllmann
2024-08-21 18:20 ` Jonathon McKitrick via Emacs development discussions.
2024-08-21 18:43 ` Gerd Möllmann
2024-08-21 20:42 ` Jonathon McKitrick via Emacs development discussions.
2024-08-22 4:02 ` Gerd Möllmann
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=87frqy5quh.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=jcm@SDF.ORG \
--cc=pipcet@protonmail.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.