blink

Just tried it! The lone interpreter itself runs flawlessly: lone <<<'(import (lone print)) (print "Hello, world!")' blink lone <<<'(import (lone print)) (print "Hello, world!")' blink lone <<<'(import (lone print) (math +)) (print (+ 1 1))' It failed to load an interpreter with a lone-embedded lisp program though. Rejected it as an invalid ELF because of a bug in my ELF editor. The embedded segments my tool generates are page aligned and end up extending past the end of the file. Linux doesn't care, it mmaps those non-existent file regions just fine as zero filled pages. Blink rejects the ELF as invalid instead. I'd say blink's behavior is correct but divergent from the Linux it's supposed to be emulating. Created issue #215 about it: https://github.com/jart/blink/issues/215 Nevertheless, I plan to push out a fix for this issue as

Really enjoyed the interview, and love the ideas behind Lone Lisp. I was curious, does it run on jart's Blink project, the tiny x86-64-linux emulator? https://github.com/jart/blink/

Also this. https://github.com/jart/blink

It's an interpreter, but it does support JIT to x64 and arm. There are some details here: https://github.com/jart/blink/?tab=readme-ov-file#technical-... On the x64-playground website it's just running as an interpreter, inside of web assembly

Nice to see my playground trending! All of this is essentially made possible by the blink engine by @jart: https://github.com/jart/blink/ Which is an x86-64-linux emulator written in a few kb of c code. There is no Backend server, everything runs locally in the browser in a runtime that weights less than a screenshot of the website itself! To implement it I modified the blink emulator to run as a C library, and compiled it into a Typescript + WASM module that exposes an emulator API. Then I built a regular web app on top of it.

How does this compare with blink [1] ? [1] https://github.com/jart/blink

Right (on x86-32 and -64, because you can’t have 64KB pages there, though larger page sizes do exist and get used). You still cannot (e.g.) MapViewOfFile() on an address not divisible by 64KB, because Alpha[1]. As far as I understand, Windows is mostly why the docs for the Blink emulator[2] (a companion project of Cosmopolitan libc) tell you any programs under it need to use sysconf(_SC_PAGESIZE) [aka getpagesize() aka getauxval(AT_PAGESZ)] instead of assuming 4KB. [1] https://devblogs.microsoft.com/oldnewthing/20031008-00/?p=42... [2] https://github.com/jart/blink/blob/master/README.md#compilin...

FWIW here's all 700 lines of Blink's x86 decoder. https://github.com/jart/blink/blob/master/blink/x86.c

blink is almost as good as qemu-user and it works great compiled with cosmocc. https://github.com/jart/blink

Why does everyone keep repeating this mantra? I wrote the x86 decoder for https://github.com/jart/blink which is based off intel's xed disassembler. It's so tiny to do if you you have the know-how to do it. master jart@studio:~/blink$ ls -hal o/tiny/blink/x86.o -rw-r--r-- 1 jart staff 23K Jun 22 19:03 o/tiny/blink/x86.o Modern microprocessors have 100,000,000,000+ transistors, so how much die space could 184,000 bits for x86 decoding really need? What proof is there that this isn't just some holy war over the user-facing design. The stuff that actually matters is probably just memory speed and other chip internals, and companies like Intel, AMD, NVIDIA, and ARM aren't sharing that with us. So if you think you understand the challenges and tradeoffs they're facing, then I'm willing to bet it's just false confidence and peanut gall

Use this link instead: https://github.com/jart/blink

There are separate static builds for aarch64 and x86_64, those are put into a "fat binary" that runs on current generation hardware/software combos (osx with aarch64, win with x86_64 and linux with both). Just building for two things is better than figuring out the whole matrix of OS vs architectures which was the other option. For other architectures like Power/armv7/i686 the software can run using the Blink project [0] [0] https://github.com/jart/blink