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

Palantir CEO Says a Surveillance State Preferable to China Winning the Al Race

https://gizmodo.com/palantir-ceo-says-a-surveillance-state-is-preferable-to-china-winning-the-ai-...
1•voxadam•1m ago•0 comments

Show HN: A DevTools-Level JavaScript API for DOM and CSS Style Rules

https://github.com/devtoolcss/chrome-inspector
1•brouser•6m ago•0 comments

The Brain's Hidden Drain

https://nautil.us/the-brains-hidden-drain-1246822/
1•fleahunter•8m ago•0 comments

Formal Requirements for Virtualizable Third Generation Architectures (1974) [pdf]

https://www.cs.cornell.edu/courses/cs6411/2018sp/papers/popek-goldberg.pdf
1•pillars•8m ago•0 comments

James Watson, who helped unravel DNA's double-helix, has died

https://arstechnica.com/health/2025/11/james-watson-who-helped-unravel-dnas-double-helix-has-died/
1•Terretta•12m ago•0 comments

Can you talk to the dead using AI?

https://www.rnz.co.nz/news/on-the-inside/578264/can-you-really-talk-to-the-dead-using-ai-we-tried...
3•billybuckwheat•14m ago•0 comments

FPGA Design Tutorial

https://blackmesalabs.wordpress.com/2024/05/27/bml-fpga-design-tutorial-part-intro/
1•pillars•17m ago•0 comments

Oddest ChatGPT leaks yet: Cringey chat logs found in Google Analytics tool

https://arstechnica.com/tech-policy/2025/11/oddest-chatgpt-leaks-yet-cringey-chat-logs-found-in-g...
3•vlod•24m ago•0 comments

CC Shop Full Data/Fresh CVV

https://cfullshop.ct.ws/
1•pauzemk•30m ago•0 comments

Why Python's deepcopy() is surprisingly slow (and better alternatives)

https://www.codeflash.ai/blog-posts/why-pythons-deepcopy-can-be-so-slow-and-how-to-avoid-it
3•misrasaurabh1•33m ago•1 comments

Zamboni Drivers Union

https://zamboni.work/
1•willswire•35m ago•0 comments

Core Product, Whole Product

https://turtlespace.blog/p/core-product-whole-product
1•surprisetalk•37m ago•0 comments

FT printed an error for 18 months and nobody noticed

https://mako.cc/copyrighteous/the-financial-times-has-been-printing-an-obvious-error-on-its-marke...
3•surprisetalk•37m ago•1 comments

The Diaper Curve

https://justismills.substack.com/p/the-diaper-curve
1•surprisetalk•38m ago•0 comments

Automat: Objects as Syntax Not Data [video]

https://www.youtube.com/watch?v=7CwxoUwY9aQ
1•surprisetalk•38m ago•0 comments

James Watson Dies at 97

https://www.cnn.com/2025/11/07/us/james-watson-death
1•sidcool•43m ago•0 comments

Who loves playing undercover game?

https://www.bestpartygames.net/games/undercover/undercover
1•Febe1212•53m ago•0 comments

GPT-OSS 120B Runs at 3000 tokens/sec on Cerebras

https://www.cerebras.ai/blog/openai-gpt-oss-120b-runs-fastest-on-cerebras
2•samspenc•54m ago•0 comments

U.S. Supreme Court allows Trump admin to avoid funding SNAP payments for now

https://www.cbc.ca/lite/story/9.6972034
5•colinprince•56m ago•4 comments

ImGui React Runtime

https://github.com/tmikov/imgui-react-runtime
2•cod1r•57m ago•0 comments

Collect the Reasons

https://collectthereasons.org/
2•erhuve•59m ago•0 comments

Omarchy 3

https://www.youtube.com/watch?v=L3EafsSCv80
2•doppp•1h ago•0 comments

Stability AI wins UK court battle against Getty Images

https://apnews.com/article/getty-stability-ai-image-copyright-trademark-fa2c561a33c7b6714a7657255...
1•gmays•1h ago•0 comments

Everyone's Getting Trapped by Hosting Renewals. Here's What I Did About It

https://veerhost.com/
1•aymanaljunaid•1h ago•0 comments

In Pictures: The race to discover the secrets of DNA

https://www.bbc.com/news/articles/c51yxlzw0w0o
1•1659447091•1h ago•0 comments

How I use AI (Oct 2025)

https://ben.stolovitz.com/posts/how_use_ai_oct_2025/
1•vinhnx•1h ago•0 comments

Big Tech's most important infrastructure is at the bottom of the sea

https://sherwood.news/tech/big-techs-most-important-infrastructure-is-at-the-bottom-of-the-sea/
1•vinhnx•1h ago•1 comments

Objective-C

https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ProgrammingWithObjecti...
2•andsoitis•1h ago•0 comments

The Farmers' Almanac Succumbs to the Digital Age

https://www.nytimes.com/2025/11/07/us/farmers-almanac-shutting-down.html
2•bookofjoe•1h ago•3 comments

Ask HN: P2P Archive.is Alternative?

2•rnmmrnm•1h ago•1 comments