Heh I thought I fixed that bug? (is it s abug?!)

This week, Mu (µ) get s bit more serious and starts to refactor the native backend (a lot). Soon™ we will support darwin/arm64, linux/arm64 and linux/amd64 (Yes, other forms of BSD will come!) – Mu (µ) also last week grew concurrency support too! 🤣

@klaxzy@klaxzy.net nothing like a blank twt eh? 😅

(#f5fb6gq) @kiwu@twtxt.net Oh? 🤔 What’s up? Can you share? Or just having a hrd time? 🤗

(#pebgp3a) @movq@www.uninformativ.de Welcome to the dark side 🤣

(#u53qyya) @movq@www.uninformativ.de I don’t think he is 🤔

(#ee3stma) @shinyoukai@neko.laidback.moe Whoohoo! That’s a start to cross-platform support 🤣

(#q33dfjq) Patch applied!

(#q33dfjq) @shinyoukai@neko.laidback.moe No email has arrived here? 🤔

(#q33dfjq) @shinyoukai@neko.laidback.moe Okay I pushed a commit that hopefully fixes this. I hope!

(#q33dfjq) @shinyoukai@neko.laidback.moe Yes; however the interpreter is also platform dependent and relies on making raw syscalls. This is so the runtime semantics remain the same between the two execution modes.

I’ll see if I can add support for linux/amd64 and netbsd/amd64 for the VM at least.

(#q33dfjq) @shinyoukai@neko.laidback.moe if you don’t show me the actual full stacktrace, I can’t fix the problem 😢

(#q33dfjq) Most of it should work on other platforms, the bytecode VM that is. You may run into some platform quirks though that rely on syscall() – Let me know what you run into and I’ll try to fix them nw. The problem right now is I haven’t even begun to start work on another platform/architecture yet.

Mu (µ) is coming along really nicely 🤣 Few things left to do (in order):

• Finish the concurrency support.
  
• Add support for sockets
  
• Add support for linux/amd64
  
• Rewrite the heap allocator
  
• Rewrite Mu (µ) in well umm Mu (µ) 😅
  

Here’s a screenshot showing off the builtin help():

(#zy5aqgq) It’s gone. 👋

(#ubuezaa) @shinyoukai@neko.laidback.moe

Work kills the soul

it sure can! 🤣

(#5wlquma) Make it so number one !

(#ubuezaa) @movq@www.uninformativ.de What’s Email?! 😂

(#533m7aa) @movq@www.uninformativ.de I quite like this part:

Many people write programs, but few stick with a program long enough to distill it.

(#fadfcsa) @bender@twtxt.net No, I had my break/holiday earlier. I chose to work through, except the public holidays of course.

(#lzax5vq) @movq@www.uninformativ.de Ahh nice! It’s been several decades since I’ve played that! Probably 3 actually come to think of it 🤣

(#lzax5vq) @movq@www.uninformativ.de what game is that?

(#fadfcsa) I basically worked through the Christmas break last year. I already had my holidays in Vietnam a few weeks earlier. 😆

Trying to build a native heap allocator that grows and isn’t statically wired into the binary’s image is fuck’n hard™ as 🤣

(#6xxkgbq) @movq@www.uninformativ.de 🤣

(#xtkev6q) @movq@www.uninformativ.de Very cool! 😎