<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 7/24/2023 10:43 AM, rabbit via Cuis-dev wrote:
<blockquote
cite="mid:3Q8-i9R-3g3KtSzEC63V5AB82Iu7WolpSYw_vsQNHEKA4kPj6L-BYl-6aA-U7BHkPhfIZi-DnF-zkMt9MfChom5m9GjfszYXSISbS4jYuEw=@callistohouse.org"
type="cite">
<div dir="auto">On reflection my curiosity is piqued. Why can’t
Spur VMs run non-spur images? The latest VM would benefit us if
it could run any image presented.<caret></caret></div>
<div><br>
</div>
<div class="protonmail_signature_block"
id="protonmail_signature_block">
<div>••• rabbit ❤️🔥🐰</div>
</div>
<div class="signature_br" contenteditable="false"><br>
</div>
<br>
</blockquote>
<br>
Spur is a different design of the object memory. Handling both in
the same VM adds extra complexity. Eliot Miranda, when he designed
and built Spur, decided on an integrated code base for VMMaker that
can handle both, and produces different executables for v3, spur32
and spur64, for various platforms, with or without the Cog jitter,
and with or without the alternative Sista bytecode set. I trust his
wisdom, and I'm more than happy using his work.<br>
<br>
Cheers,<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich</pre>
</body>
</html>