<p><span class="h-card" translate="no"><a href="https://mastodon.social/@unspeaker" class="u-url mention">@<span>unspeaker</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> for instance when Apple transitioned the Macintosh from 68K to PowerPC, the system still booted into a 68K emulator by default. but &quot;universal procedure pointers&quot; used a trap instruction to break out of the emulator, followed by a data structure describing how to marshal arguments and returns to the native PowerPC code and back <a href="https://orangejuiceliberationfront.com/universal-procedure-pointers/" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">orangejuiceliberationfront.com</span><span class="invisible">/universal-procedure-pointers/</span></a></p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@unspeaker" class="u-url mention">@<span>unspeaker</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> so WoW64 works by setting up a 32-bit code segment in the process during the 64-bit process&#39;s startup. the 32-bit system DLLs contain &quot;thunks&quot; that call into the real 64-bit system after marshalling arguments and returns across the different platform conventions.</p><p>it can do this on x86-64 CPUs because the hardware supports both the 32-bit and 64-bit instruction sets in one process. but one platform or the other could also be emulated using similar techniques</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@film_girl" class="u-url mention">@<span>film_girl</span></a></span> Same. Black console, white controller for now.</p>

<p>Analogue 3D acquired!</p>

<p><span class="h-card" translate="no"><a href="https://chaosfem.tw/@Orc" class="u-url mention">@<span>Orc</span></a></span> i think amazon sends me a message and the message is a deafeningly unsubtle &quot;be more racist, you piece of shit&quot;</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>whitequark</span></a></span> *blink*</p><p>That is sure an <em>eclectic</em> choice at the end of the list there.</p>

<p><span class="h-card" translate="no"><a href="https://f.duriansoftware.com/@joe" class="u-url mention">@<span>joe</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> </p><p>this stuff is exciting! i think i could use a similar approach to shim abandoned closed-source music plugins (win32 vst2) into to a format i can use on linux</p><p>even started looking into it (<a href="https://mastodon.social/@unspeaker/113324660678159093" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@unspeaker/113</span><span class="invisible">324660678159093</span></a>). suppose i statically link the required dlls&#39; wine equivalents to the plugin? what can i use to adapt between 32 and 64 bit tho? i remember linux multiarch being a hassle</p><p>the vst2&lt;-&gt;$modernpluginformat shim obj i guess i&#39;d have to write myself (in rust no_std?)</p>

<p>nvm it was an accident</p>

<p>this might be the first system of measurement with &quot;American&quot; in the name that I actually respect</p>