Timeline Sandbox

Conversation

Recent posts in reply to #q33dfjq

@prologic@twtxt.net

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():

Read replies 2 months ago
@prologic@twtxt.net

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.

In reply to: #q33dfjq 2 months ago
@prologic@twtxt.net

@shinyoukai if you don't show me the actual full stacktrace, I can't fix the problem 😢

In reply to: #q33dfjq 2 months ago
@prologic@twtxt.net

@shinyoukai 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.

In reply to: #q33dfjq 2 months ago
@prologic@twtxt.net

@shinyoukai Okay I pushed a commit that hopefully fixes this. I hope!

In reply to: #q33dfjq 2 months ago
@prologic@twtxt.net

@shinyoukai No email has arrived here? 🤔

In reply to: #q33dfjq 2 months ago
@prologic@twtxt.net

Patch applied!

In reply to: #q33dfjq 2 months ago
Comment via email