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.

RFV-0001: Request for Vibes

https://tomaytotomato.com/request-for-vibes/
1•tomaytotomato•2m ago•0 comments

Why We Ignore Advice

https://yusufaytas.com/why-we-ignore-advice
6•yusufaytas•3m ago•0 comments

New Linux kernel security bug; Fragnesia

https://www.openwall.com/lists/oss-security/2026/05/13/3
1•tankenmate•3m ago•0 comments

Ask HN: How to Invest 10K EUR

2•default_•3m ago•0 comments

Harvard Votes on Limiting "A" Grades

https://www.axios.com/local/boston/2026/05/11/harvard-faculty-vote-grade-inflation-cap-a-grades-i...
1•smurda•4m ago•0 comments

What happened to the car designed for women, by women?

https://uxdesign.cc/what-happened-to-the-car-designed-for-women-by-women-1fdcde8a0bc4
1•rmason•5m ago•1 comments

The AI Apocalypse

https://www.youtube.com/watch?v=8nsxuB3Vsts
1•indigodaddy•6m ago•0 comments

Continuous lamination unlocks production of large-area flexible circuit boards

https://techxplore.com/news/2026-04-lamination-stable-production-large-area.html
2•PaulHoule•8m ago•0 comments

Hilary Putnam: Brains in a Vat (1981)

https://www.cambridge.org/core/books/abs/reason-truth-and-history/brains-in-a-vat/4301D7FCC586969...
2•brudgers•9m ago•0 comments

We built the fastest database for querying large agent traces using Rust

https://www.langchain.com/blog/introducing-smithdb
1•palashshah•9m ago•0 comments

Princeton mandates proctoring in-person exams, upending 133 years of precedent

https://www.dailyprincetonian.com/article/2026/05/princeton-news-adpol-proctoring-in-person-exami...
6•bookofjoe•10m ago•0 comments

GitHub Copilot individual plans: Introducing flex allotments

https://github.blog/news-insights/company-news/github-copilot-individual-plans-introducing-flex-a...
1•dougskinner•10m ago•0 comments

Ask HN: Why does my ChatGPT always display one sentence per line?

1•djyde•11m ago•0 comments

Show HN: Arrivl – Analytics for AI agent traffic on your site

https://arrivl.ai
1•starfun•11m ago•0 comments

Show HN: Vibe-coding video games with Claude (Day 30: Chess)

https://gamevibe.us/30-chess
1•pzxc•12m ago•0 comments

500 Lines or Less: An Archaeology-Inspired Database

https://aosabook.org/en/500L/an-archaeology-inspired-database.html
1•smartmic•12m ago•0 comments

Exploring the HTML-in-Canvas Proposal

https://tympanus.net/codrops/2026/05/13/exploring-the-html-in-canvas-proposal/
1•motiontx•12m ago•0 comments

Authenticity in Creative Expression with AI

https://postcorporate.substack.com/p/good-morning-dr-chandra-this-is
1•gnostikka•12m ago•0 comments

How to Achieve Truly Serverless GPUs

https://modal.com/blog/truly-serverless-gpus
1•birdculture•13m ago•0 comments

Omaha as Judgment Day for AGI

https://mayankagrawalphd.substack.com/p/omaha-as-judgment-day-for-agi
2•timshell•14m ago•0 comments

There Is a Fire Sale on M.B.A.s

https://www.wsj.com/lifestyle/careers/there-is-a-fire-sale-on-m-b-a-s-87d56c69
3•harambae•14m ago•0 comments

Notion's Agents SDK

https://twitter.com/NotionDevs/status/2054600927810920894
2•umangsehgal93•16m ago•0 comments

Claude helped recover 5 BTC that was thought lost for 11 years

https://twitter.com/cprkrn/status/2054586810475364536
2•serial_dev•17m ago•0 comments

Local Android emulation in an AI agent

https://docs.devin.ai/onboard-devin/environment/android-emulation
1•Alextigtig•19m ago•0 comments

Adopting Helix*Isms

https://kristun.dev/posts/adopting-helix-isms/
1•polyamid23•19m ago•0 comments

AI in Bio Biggest Questions

https://shelbyann.substack.com/p/biggest-questions-in-biotech
1•cellsnstuff•19m ago•0 comments

Everything Claude Code: performance optimization system for AI agent harnesses

https://github.com/affaan-m/everything-claude-code
1•doener•21m ago•0 comments

Rars: a Rust RAR implementation, mostly written by LLMs

https://bitplane.net/log/2026/05/rars/
8•davidsong•22m ago•3 comments

Agents Window in VS Code

https://code.visualstudio.com/docs/copilot/agents/agents-window?source=vsc-website-banner
2•nor0x•23m ago•0 comments

Type-driven design in automotive C: how much of my code is manual type checking?

https://lmilz.dev/blog/2025/12/11/From-Defensive-Programming-to-Type-Driven-Design.html
1•lmilz•25m ago•0 comments