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•10mo 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•10mo 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•10mo 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•10mo 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.

Opus 4.7 Became Better at Web Design

https://www.yashthapliyal.com/blog/opus-4-7-web-design
1•yash1hi•2m ago•0 comments

Write broken commits for better review

https://huonw.github.io/blog/2026/04/broken-commits/
1•dbaupp•2m ago•0 comments

Ask HN: How did you get your first users with zero audience?

1•arikusi•4m ago•0 comments

I built send/links to stop losing links across tabs, bookmarks, and chats

https://sendlinks.app
1•prashantchanne•5m ago•0 comments

Characterizing the Impact of Congestion in Modern HPC Interconnects

https://arxiv.org/abs/2604.11432
1•matt_d•5m ago•0 comments

Stop Using JWTs

https://gist.github.com/samsch/0d1f3d3b4745d778f78b230cf6061452
1•birdculture•6m ago•0 comments

Shipfast.py – SaaS Starter Kit for Python Devs (FastAPI and Supabase and Stripe)

https://www.shipfastpy.com/
1•brandocalricia•8m ago•1 comments

The Long Hunt for China's Vanishing Elephant Slides

https://www.sixthtone.com/news/1018428
1•sohkamyung•8m ago•0 comments

Aliens.gov Resolves – To a WordPress "Site Not Found" Error

4•ascarola•10m ago•2 comments

Mechanics' institute

https://en.wikipedia.org/wiki/Mechanics%27_institute
1•hhs•10m ago•0 comments

Accessing Hardware in Rust

https://ferrous-systems.com/blog/hardware-access-rust/
1•PaulHoule•11m ago•0 comments

Rewiring financial services to scale intelligence

https://www.valtech.com/blog/rewiring-financial-services-to-scale-intelligence/
1•mooreds•12m ago•0 comments

Anubis weighs the soul of incoming HTTP requests to stop AI crawlers

https://github.com/TecharoHQ/anubis
2•rzk•12m ago•0 comments

Show HN: Rebuilt SETI Home but for AI

https://github.com/Agent-FM/agentfm-core
3•s4saif•13m ago•2 comments

Tessera: Unlocking Heterogeneous GPUs Through Kernel-Granularity Disaggregation

https://arxiv.org/abs/2604.10180
1•matt_d•17m ago•0 comments

Natural Selection Shaped Humanity

https://www.economist.com/science-and-technology/2026/04/15/how-natural-selection-really-shaped-h...
2•andsoitis•18m ago•0 comments

Big Tech's $300M election war chest rattles Democrats

https://www.ft.com/content/7529e4cd-e336-4b75-917b-84f91bc48437
1•petethomas•19m ago•0 comments

I Invented Lattice and Isomorphic Computing

https://github.com/aevov/afolabi-unified-framework
1•wakanda-island•21m ago•1 comments

Show HN: NoFS – What if files are just projections, graph is the truth?

https://nofs.ai/
1•mmethodz•26m ago•0 comments

Casus Belli Engineering

https://marcosmagueta.com/blog/casus-belli-engineering/
1•schonfinkel•33m ago•0 comments

Closure of Radio 4 on Long Wave (LW)

https://www.bbc.co.uk/reception/work-warning/news/radio4lw
2•austinallegro•34m ago•1 comments

Grpo explained: group relative policy optimization for LLM finetuning

https://cgft.io/learn/grpo-intro/
1•kumama•35m ago•0 comments

U.S. to Create High-Tech Manufacturing Zone in Philippines

https://www.wsj.com/world/asia/u-s-to-create-high-tech-manufacturing-zone-in-philippines-017c1668
12•dcgudeman•36m ago•7 comments

15% of Reddit Posts are Likely AI-generated in 2025

https://originality.ai/blog/ai-reddit-posts-study
3•akyuu•37m ago•2 comments

Street Fighter 2026 Trailer

https://www.youtube.com/watch?v=gX0Btbbddxk
3•havblue•40m ago•1 comments

Reed Hastings is leaving Netflix after 29 years

https://www.engadget.com/entertainment/streaming/reed-hastings-is-leaving-netflix-after-29-years-...
2•andsoitis•40m ago•0 comments

Helpful translations from British English (2015)

https://www.independent.co.uk/news/uk/home-news/chart-shows-what-british-people-say-what-they-rea...
1•worik•41m ago•1 comments

Unicorn Market Cap 2026: SF Is the GenAI Super Cluster

https://blog.eladgil.com/p/unicorn-market-cap-2026-sf-is-the
1•gmays•43m ago•0 comments

Ollama v0.21.0-Rc0

https://github.com/ollama/ollama/releases/tag/v0.21.0-rc0
1•maxloh•43m ago•0 comments

Release PiClaw v1.8.0 – This Is Spinal Tap

https://github.com/rcarmo/piclaw/releases/tag/v1.8.0
2•rcarmo•44m ago•0 comments