frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Show HN: Brainfuck to RISC-V JIT compiler written in Zig

https://github.com/evelance/brainiac
5•0x000xca0xfe•11mo ago
Hi everybody,

this was my project to learn Zig and RISC-V+x86_64 assembly.

Not sure if anybody is actually interested in yet another Brainfuck compiler, so I'll just write up some random things I learned while building it!

- A primitive assembly stitching compiler is 10x faster than the interpreter. Did not expect that.

- The generated x86 code is really bad (e.g. it always uses 6 or 7 byte sized instructions with 32-bit immediates when there are much smaller ones) but it doesn't really matter. Good code generated by GCC and clang for transpiled Brainfuck->C is not much faster as it's bottlenecked by memory accesses anyways.

- Zig is pretty far along actually. You can make serious projects with it!

- But the community seems to like self-punishment. Unused parameters and variables are hard errors and there is no way to disable that even for debug builds. Makes quickly commenting out part of the code a real PITA.

- I've had a miscompilation due to std.mem.span being broken and two source code breaks going from Zig 0.13 to 0.15 (std.mem.page_size got removed and ArrayList.popOrNull as well).

- But arbitrary size integers are fantastic! And well-defined two's complement behaviour!

Here is for example the code that encodes the c.beqz instruction:

  /// Branch if Equal to Zero (compressed): c.beqz rs1', offset -> beq rs1, x0, offset
  pub fn c_beqz(text: *std.ArrayList(u8), rs1: RV_X, offset: i9) !void {
      std.debug.assert(is3BitReg(rs1));
      std.debug.assert(@mod(offset, 2) == 0);
      const imm: u9 = @bitCast(offset);
      const RV_CB = packed struct(u16) {
          op: u2,
          offset5: u1,
          offset1_2: u2,
          offset6_7: u2,
          rsd_rs1_: u3,
          offset3_4: u2,
          offset8: u1,
          funct3: u3,
      };
      const ins = RV_CB {
          .op = 0x1,
          .offset5 = @truncate(imm >> 5),
          .offset1_2 = @truncate(imm >> 1),
          .offset6_7 = @truncate(imm >> 6),
          .rsd_rs1_ = @truncate(@intFromEnum(rs1) - 8),
          .offset3_4 = @truncate(imm >> 3),
          .offset8 = @truncate(imm >> 8),
          .funct3 = 0x6,
      };
      try appendInstruction(text, u16, @bitCast(ins));
  }
This is really nice as all the exotic integer sizes are actually checked, too.

- Zig support for Windows is good. Porting the project to Windows was very easy.

- When the RISC-V registers are carefully chosen, almost all instructions could be compressed in this projects.

- Compressed instructions and good branching code (using the branch instructions directly when the jump range is small enough instead of branching over a larger jump instruction) did not noticeably change performance on real hardware (OrangePi RV2).

- But somehow QEMU got a massive boost from that. Not sure why exactly.

So, that's about it!

I hope at least something was interesting...

Comments

sylware•11mo ago
thumbs up for this project (everything RISC-V is usually).

I write rv64 assembly (nearly core only, without memory reservation instructions) and run it on x86_64 with a very small (x86_64 assembly written) interpreter.

And your are right, I have had thoughts about a "RISC-V" x86_64 compiler (but it will probably require some runtime unfortunately).

Hopefully, rv22+ hardware with ultra-performant µ-architecture and with the latest silicon process will happen sooner than we expect. One less PI toxic lock and cleaner, _really standard_ assembly (the end game of much software).

0x000xca0xfe•11mo ago
Yeah I can't wait for a performant RISC-V core. Runtime code generation is so easy for RISC-V. I have many ideas or projects where I'd like to use it but it feels kinda pointless when JITed RISC-V machine code on current hardware gets destroyed by any half-decent x86 PC or Mac running naive C code.
sylware•11mo ago
Well, here are the tricks: interpreted rv64 assembly will be "slow"... actually "slower" than x86_64 native code... but in many execution contexts, for many pieces of software, here the first trick: the "slow" interpreted rv64 assembly machine code will be... "fast" enough... The 2nd trick: I have control on my rv64 machine interpreter, and I can write native x86_64 acceleration assembly along side of a rv64 reference implementation (I planned to do just that for my CPU renderer in my wayland compositor... actually I have already AVX2 code for some of that, even though the sweet spot is AVX512, but don't have the hardware for this, yet).

And once we have this rv64 shiny hardware, certainly won't be a drop-in, but the distance to code will be minimal.

One important SDK thing: I am careful at using the smallest number of rv64 machine instructions (we tend to forget 'R' in "RISC-V" means 'R'educed...), and I use basic, really basic, C preprocessors instead of the assembler preprocessor in order to decouple the assembly code from a specific assembler preprocessor. I don't even use assembler pseudo-instructions, or ABI register names, neither compressed machine instructions.

On top of that: I don't use ELF, I use a super minimal executable/system interface dynamic shared library format of my own, omega idiotically simple, which I wrap in ELF binaries for transparent support. People have to come to realize, ELF complexity, for a executable/system interface dynamic shared library is utterly and completely obsolete, even a liability once you are looking for binary stability in time (cf games), proven over more than the last decade.

Company said I could move and then changed their mind

https://www.askamanager.org/2026/04/company-said-i-could-move-and-then-changed-their-mind-how-do-...
1•mooreds•3m ago•0 comments

Show HN: I made a simulator for personal finance (5 year update)

https://projectionlab.com/
1•scubakid•5m ago•0 comments

Custom Voices and Voice Library

https://x.ai/news/grok-custom-voices
1•tjek•7m ago•0 comments

I'm a late arrival to short-form video – its effect on my life has shocked me

https://www.theguardian.com/commentisfree/2026/may/03/algorithm-short-form-video-overload
1•andsoitis•8m ago•0 comments

Sandwich Theorem

https://en.wikipedia.org/wiki/Squeeze_theorem
1•_Microft•11m ago•0 comments

Pipelight

https://pipelight.dev/
1•fulafel•12m ago•0 comments

After giving away $26B MacKenzie Scott's wealth remains largely unchanged

https://timesofindia.indiatimes.com/world/us/after-giving-away-26-billion-in-philanthropy-mackenz...
1•gscott•13m ago•0 comments

The Lobster in the Hot Pot – OpenTentacle

https://opententacle.com/article/2026-04-05/
1•birdculture•13m ago•0 comments

Dogs' brains began to shrink at least 5k years ago

https://www.theguardian.com/science/2026/apr/29/dogs-brains-shrink-5000-years-ago
1•gmays•14m ago•0 comments

What are the chances a hurricane will hit my home?

https://www.noaa.gov/stories/what-are-chances-hurricane-will-hit-my-home
1•bilsbie•15m ago•0 comments

How the JVM Optimizes Generic Code – A Deep Dive [pdf]

https://cr.openjdk.org/~jrose/pres/202603-SpecializedGeneric.pdf
2•Tomte•17m ago•0 comments

I rebuilt my blog's cache. Bots are the audience now

https://hoeijmakers.net/thirty-years-of-caching-sorted-in-an-afternoon/
3•robhoeijmakers•18m ago•0 comments

Robotics startups are losing to slow feedback loops

https://www.simbiotic.dev/blog/robotics-startup-development-speed
1•nikhilol•18m ago•0 comments

I completed 100 Days of Java over 5 years and mapped the journey as a graph

https://mohibulsblog.netlify.app/java/100daysofjava/graph/
1•celurian92•25m ago•1 comments

Learn concurrency – a deep dive into multithreading with Python

https://blog.geekuni.com/2026/04/python-concurrency.html
2•aquastorm•26m ago•0 comments

StackGraveyard.dev – Live mortality scores for NPM packages

https://www.stackgraveyard.dev/
1•tlseternal•27m ago•0 comments

What If Your Boss Monitored Your Emotions?

https://www.theatlantic.com/culture/2026/05/worker-surveillance-emotion-ai/687029/
2•Brajeshwar•27m ago•1 comments

1984 Called: It predicted our AI-obsessed reality

https://medium.com/@tk512/the-ai-predictions-in-the-movie-electric-dreams-1984-0c6a47a6326e
1•sgt•28m ago•0 comments

What Makes Art Great

https://nabeelqu.substack.com/p/what-makes-art-great
1•jger15•30m ago•0 comments

OpenAI delays ChatGPT "adult mode"

https://www.axios.com/2026/03/06/openai-delays-chatgpt-adult-mode
1•embedding-shape•31m ago•0 comments

Benchmarking local LLMs against coding agent harnesses [WIP]

https://neuralnoise.com///2026/harness-bench-wip/
1•Terretta•33m ago•0 comments

Virtual violin produces realistic sounds

https://news.mit.edu/2026/mit-engineers-virtual-violin-produces-realistic-sounds-0429
1•gmays•34m ago•0 comments

How vLLM Works

https://avkcode.github.io/blog/how-vllm-works.html
2•IngessLabs•35m ago•1 comments

Gerry Conway, creator of the Punisher in Spider-Man comics, dies at 73

https://www.theguardian.com/culture/2026/may/01/gerry-conway-punisher-spider-man-comics
1•bookofjoe•36m ago•0 comments

Show HN: Next-gen music visualization in the browser

https://vizz.fm/
2•lowtecky•37m ago•2 comments

Why you're more likely to buy something for $4.99 than $5.00

https://thehustle.co/originals/why-youre-more-likely-to-buy-something-for-499-than-500
1•Anon84•37m ago•0 comments

Koch Brothers' covert operations (2010)

https://www.newyorker.com/magazine/2010/08/30/covert-operations
2•simonebrunozzi•40m ago•0 comments

VSCode now adds Copilot as a co-author of all your commits

https://bsky.app/profile/majormcdoom.bsky.social/post/3mkvqyjtlqc25
2•doener•42m ago•0 comments

Meditations on Moloch (2014)

https://slatestarcodex.com/2014/07/30/meditations-on-moloch/
1•simonebrunozzi•44m ago•0 comments

Running official Arch Linux on Arm (not to be confused ArchLinuxARM)

https://charon.konekopi.com/posts/archlinux_on_arm/
1•Charon77•47m ago•0 comments