(#yiihgta) @movq@www.uninformativ.de Is this on yout little toy OS? 🤔

(#dhngcaq) @lyse@lyse.isobeef.org I can tell you this right now, writing assembly / machine code is fucking hard work™ 😓 I’m sure @movq@www.uninformativ.de can affirm 🤣 And when it all goes to shit™ (which it does often), man is debugging fucking hard as hell! Without debug symbols I can’t use the regular tools like lldb or gdb 😂

(#xupmaxa) @lyse@lyse.isobeef.org Yeah I remember you said some days back that your interest in compilers was rekindled by my work on mu (µ) 😅

Whoo! I fixed one of the hardest bugs in mu (µ) I think I’ve had to figure out. Took me several days in fact to figure it out. The basic problem was, println(1, 2) was bring printed as 1 2 in the bytecode VM and 1 nil when natively compiled to machine code on macOS. In the end it turned out the machine code being generated / emitted meant that the list pointers for the rest... of the variadic arguments was being slot into a register that was being clobbered by the mu_retain and mu_release calls and effectively getting freed up on first use by the RC (reference counting) garbage collector 🤦‍♂️

(#pact6sq) @lyse@lyse.isobeef.org True !

(#o3hv4aq) @zvava@twtxt.net The problem you now then is you lose integrity of the message content if you compute the hashes at runtime rather than on the way in. So if your message content or database becomes corrupt in any way, so do your hashes.

Building native compilers is hard 🤣 Building bytecode VM / interpreters is way easier 🤣

(#7igza6q) @shinyoukai@neko.laidback.moe Very cool! 😎

(#7igza6q) @shinyoukai@neko.laidback.moe Nice! 👍

(#kaiqxgq) @movq@www.uninformativ.de Thanks! 🙏

(#kaiqxgq) @shinyoukai@neko.laidback.moe Nah it’s more like there’s a lot of repeated code, because when you go from source language to intermediate representation to machine code, well you just end up writing a lot of the same patterns over and over again. I need to dedupe this I think.

(#vzawhtq) @kiwu@twtxt.net Ooof 😢 That’s rough!

(#kaiqxgq) The compiler technique I’m using here is to not “emit” most of the runtime if it’s actually never used in your program, and also dropping dead code in the SSA pass.

(#kaiqxgq) @movq@www.uninformativ.de I’ve managed to bring a simple “Hello World!” in mu (µ) (at least on macOS / Darwin / ARM64) down to ~86KB (previously ~146KB) 🥳

Hmmm I need to figure out a way to reduce the no. of lines of code / complexity of the ARM64 native code emitter for mu (µ). It’s insane really, it’s a whopping ~6k SLOC, the next biggest source file is the compiler at only ~800 SLOC 🤔

(#gslvc3q) @movq@www.uninformativ.de I think I can get binaries even smaller with a bit more work and effort 🤔 But yeah still working on the native code generation (at least for macOS targets)

(#gslvc3q) @movq@www.uninformativ.de Oh that’s fine, Mu can compile to native code and so far binaries. at least on macOS are in the order of Kb in size 😂

(#gslvc3q) @movq@www.uninformativ.de It’d be cool if you could get µ (Mu) running in your little toyOS 🤣 You’d technically only have to swap out the syscall() builtin for whatever your toy OS supports 🤔

(#jvgxb7q) @thecanine@twtxt.net I see 🤔 Very cool though! 😎

(#txkctuq) @movq@www.uninformativ.de I watched a few of these thanks to you! Very cool shit™ 😎

(#axubhsq) @movq@www.uninformativ.de Ooof that’s chilly 🥶

that’s a whopping 36°C today 🥵

(#eko3fpa) @dce@hashnix.club merry Christmas to you too!

(#jvgxb7q) @thecanine@twtxt.net Is it because you’ve used white pixels around it to sort of give it aht 3D look? 👀 Hmm? 🤔

(#hridn7a) @bender@twtxt.net It’s fun living in the future isn’t it 🤣

👋 Merry Xmas 🎄 🎅

👋 Merry (2025) Xmas y’all 🎄 Ho ho ho! 🎅

(#c6rrdzq) @movq@www.uninformativ.de From 2:50 PM to 3:23 PM AEST (+10 UTC) there was an outage. Everything went “up” on Down Detector, my EU region went offline, numerous sites were unavailable, and so on. Basically everything to/from the EU appeared to basically go kaput.

Hey EU friends 👋 wtf happened to the EU Internet today for about 40 minutes or so?