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.

Why mathematicians are boycotting their biggest conference

https://www.scientificamerican.com/article/why-mathematicians-are-boycotting-their-biggest-confer...
1•nickcotter•5m ago•0 comments

Mathematics Is All You Need

https://zenodo.org/records/19080172
1•vinhnx•9m ago•0 comments

Carl Schmitt in Miami

https://thecritic.co.uk/carl-schmitt-in-miami/
1•paulpauper•11m ago•0 comments

How Many AA Batteries Does It Take to Power a PC Setup? [video]

https://www.youtube.com/watch?v=U5lskFXDbWs
1•gnabgib•12m ago•0 comments

Caching algorithms without knowing how they work

https://blog.autorouting.com/p/caching-algorithms-without-knowing
1•juanpabloaj•13m ago•0 comments

Will This 'Miracle' Battery Change Your Mind About EVs?

https://www.wsj.com/lifestyle/cars/donut-lab-solid-state-battery-ssb-ev-4e6ad966
1•NN88•18m ago•1 comments

Solving the Strait of Hormuz Blockage

https://www.austinvernon.site/blog/thestrait.html
1•paulpauper•18m ago•0 comments

Airfare Is Just the Beginning

https://www.theatlantic.com/newsletters/2026/03/expensive-plane-tickets-oil-iran/686604/
2•paulpauper•19m ago•0 comments

Stop picking my Go version for me

https://blog.howardjohn.info/posts/go-mod-version/
1•ingve•19m ago•0 comments

Show HN: EnterpriseFizzBuzz – 622K lines of production-grade FizzBuzz

https://github.com/Elijah-J/EnterpriseFizzBuzz
2•CodeIsMyFetish•23m ago•0 comments

AI Perfected Chess. Humans Made It Unpredictable Again

https://www.bloomberg.com/news/articles/2026-03-27/ai-changed-chess-grandmasters-now-win-with-unp...
2•GMoromisato•28m ago•1 comments

Show HN: Windows 95–style Weather App for iPhone

https://apps.apple.com/us/app/weather-exe/id6761195944
1•web3rb•28m ago•0 comments

Intel Core Ultra Series 3 VPro: 18A AI PCs Debut with Dtect Security Updates

https://hothardware.com/news/intel-unveils-core-ultra-series-3-vpro
1•rbanffy•34m ago•0 comments

Goldman Sachs now reckons that oil could take out the 2008 record of $147

https://www.ft.com/content/360ca227-4d2a-41a4-a05f-41baedc0f7d2
3•bookofjoe•34m ago•1 comments

Causality optional? Testing the "indefinite causal order" superposition

https://arstechnica.com/science/2026/03/getting-formal-about-quantum-mechanics-lack-of-causality/
1•rbanffy•34m ago•0 comments

Show HN: Drag-to-Reveal Before/After Slider Component for React/Next.js

1•doanything_ai•35m ago•1 comments

Russia took satellite images of U.S. base before Iranian attack, Zelensky says

https://www.nbcnews.com/world/ukraine/russia-us-base-american-troops-zelenskyy-rcna265612
1•vrganj•36m ago•0 comments

Suspect in Foiled Bank of America Attack Says He Was Recruited on Snapchat

https://www.newsweek.com/suspect-in-foiled-bank-of-america-attack-says-he-was-recruited-on-snapch...
1•geox•38m ago•0 comments

I built PistonAlpha to track the collector car market in real time

https://pistonalpha.com/
1•magrix•39m ago•0 comments

The Cryptopals Crypto Challenges

https://cryptopals.com/
1•pmaddams•39m ago•0 comments

The Braille Institute's family of hyperlegible fonts

https://www.brailleinstitute.org/freefont/
2•pmaddams•40m ago•0 comments

Benchmarking quantum simulation with neutron-scattering experiments

https://arxiv.org/abs/2603.15608
1•rbanffy•40m ago•0 comments

MCP Toolbox for Databases

https://github.com/googleapis/genai-toolbox
1•pmaddams•41m ago•0 comments

Old masters, new perspectives: The Gemäldegalerie in Berlin

https://blog.google/company-news/outreach-and-initiatives/arts-culture/old-masters-new-perspectiv...
2•gnabgib•41m ago•0 comments

Claude-IPC: Watch 5 claudes build a terminal Yubikey manager together [video]

https://www.youtube.com/watch?v=6vEJNr8sASI
1•thejabberwock•43m ago•1 comments

Is AI agent discoverability a reputation graph problem, not an SEO problem?

https://www.snackonai.com/p/the-web-of-trust-will-be-the-next-distribution-layer
1•mohinish•50m ago•0 comments

Private equity turned vulnerable elderly people into human ATMs

https://www.theguardian.com/society/2026/mar/28/the-great-care-home-cash-grab-how-private-equity-...
27•mordechai9000•52m ago•8 comments

OpenClaw is fun. OpenClaw is dangerous. Here's where Tailscale helps

https://tailscale.com/blog/openclaw-tailscale-aperture-serve
2•makaimc•52m ago•0 comments

U.S. uses hundreds of Tomahawk missiles on Iran, alarming some at Pentagon

https://www.washingtonpost.com/national-security/2026/03/27/iran-war-tomahawk-missiles/
3•breve•53m ago•0 comments

Left Atrial Appendage Closure or Anticoagulation for Atrial Fibrillation

https://www.nejm.org/doi/full/10.1056/NEJMoa2517213
1•bookofjoe•54m ago•0 comments