Re: MPS: Problem with dynamic modules

[Eli Zaretskii <eliz@gnu.org>]

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: eller.helmut@gmail.com,  emacs-devel@gnu.org
> Date: Sun, 19 May 2024 15:58:28 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> As a pseudo-vector, R moves, and &R->value changes when it does. And so,
> >> Fapply in the vterm modules becomes invalid.
> >
> > Can we prevent the pseudo-vector R from moving?
> 
> I'm not sure.
> 
> MPS has an AMS pool class (mark-sweep, non-moving) that could work.
> Alas, they say themselves that is not production-ready. And on reading
> the reference again
> 
>   https://memory-pool-system.readthedocs.io/en/latest/pool/ams.html#pool-ams

No, I mean tell the pool we are using now that this vector cannot be
moved.  AFAIU, this should be possible, and we do that in other cases,
no?

> Another idea would be to malloc R->value and return R->value instead of
> &R->value. But I have not the slightest idea what consequences that
> might possibly have in terms of leaking abstractions and compatibilty.
> Maybe a module expert could tell.

Daniel, can you help here?