🚀 go-pugleaf

One problem with trampolines and self-modifying code is that there
is no longer a separate, read only code space. This can complicate
code sharing by demand paging (self-mod code), and be influenced by
the processor's caches and prefetch queues, if self-modifying code is
expected to work under all circumstances.
 I know for a fact that some CPU testers find out about perfectly
object-code compatible CPUs by finding out, under which circumstances
in self-modifying code is the old code executed instead of the
modified one.

The real problem is dealing with separate code space cache controllers,
which are likely not to be designed for that purpose.