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

Political market entropy in Rome. An analysis of different electoral cycles

https://www.frontiersin.org/journals/political-science/articles/10.3389/fpos.2026.1744381/full
1•PaulHoule•34s ago•0 comments

Show HN: Readme badge to quickly find related open source repos

https://relatedrepos.com/badge
1•plurch•1m ago•0 comments

Apollo sued for allegedly concealing Epstein business ties from shareholders

https://www.reuters.com/sustainability/boards-policy-regulation/apollo-leon-black-sued-allegedly-...
1•petethomas•2m ago•0 comments

Free Software Needs Free Tools: Making Your Project Open

https://cfp.cfgmgmtcamp.org/ghent2026/talk/LHWU8T/
1•Tomte•2m ago•0 comments

Show HN: A Write Barrier That Blocks Structural Collapse in LLM Reasoning

1•persistentVlad•2m ago•1 comments

Show HN: Exodus – we tracked 240 moves across companies to map the AI talent war

https://7min.ai/exodus/
1•fabioperez•3m ago•0 comments

Designing Search Experiences

1•CShorten•4m ago•0 comments

Deploy from GitHub Actions without Storing Secrets (Using OIDC)

https://www.even.li/posts/2026-03-03-deploy-github-actions-without-storing-secrets-using-oidc/
1•n_e•5m ago•0 comments

Two Months as a Vibe Coder

https://www.pinchofintelligence.com/two-months-as-a-vibe-coder/
1•rmeertens•5m ago•0 comments

Finance in the Dark

https://www.phenomenalworld.org/analysis/finance-in-the-dark/
1•speckx•5m ago•0 comments

I made the first eSIM service for OpenClaw

https://www.getesimpal.com/en-US/agents
1•deniurchak•7m ago•1 comments

The 10x inference tax you don't have to pay

https://www.distillabs.ai/blog/the-10x-inference-tax-you-dont-have-to-pay
1•maciejgryka•8m ago•0 comments

Show HN: Aside – Local meeting capture with vault-native AI distillation

https://github.com/jshph/aside/
1•jphorism•8m ago•0 comments

Package Management Is Naming All the Way Down

https://nesbitt.io/2026/03/03/package-management-is-naming-all-the-way-down.html
1•zdw•9m ago•0 comments

Plasma Bigscreen – 10-foot interface for KDE plasma

https://plasma-bigscreen.org
1•birdculture•9m ago•0 comments

Darwinian Post-Design

https://medium.com/@big.sebastian.ionut/darwinian-post-design-when-ease-of-use-becomes-the-only-h...
1•levabalkin•10m ago•1 comments

Qatar Shuts World’s Largest LNG Export Plant

https://www.bloomberg.com/news/articles/2026-03-02/european-gas-rallies-more-than-30-as-qatar-hal...
2•geox•11m ago•0 comments

Show HN: Kai – macOS native fully autonomous AI agent.

https://www.hikai.space
2•StephaneBessa•12m ago•0 comments

Invite people over to your home regularly

https://blog.mattglassman.net/you-should-invite-people-over-to-your-home-regularly/
2•speckx•14m ago•0 comments

Show HN: Potatoverse, home for your vibecoded apps

https://github.com/blue-monads/potatoverse
2•born-jre•15m ago•0 comments

Migrating Elderly Care AI from Qwen 3 to 3.5 on Apple Silicon – 14x Latency Fix

https://medium.com/@aejaz.sheriff/from-qwen-3-to-qwen-3-5-on-apple-silicon-a-14x-latency-regressi...
2•asqpl•16m ago•1 comments

Show HN: AI Home Design – Room redesign and video tour and 3D panorama

https://aihomedesign.io
2•Evanmo666•17m ago•0 comments

Jacinda Arderns move to Australia spotlight on New Zealand's brain drain problem

https://www.bbc.com/news/articles/clyx93597l4o
1•tartoran•17m ago•0 comments

Iran Just Triggered a Cryptic Shortwave Message [video][8m41s]

https://www.youtube.com/watch?v=ErmbTpxAM7Q
1•Bender•18m ago•0 comments

We may soon have 70M boomers too old to drive, too car-dependent to stop

https://lloydalter.substack.com/p/we-may-soon-have-70-million-boomers
4•cainxinth•18m ago•0 comments

Are AI Datacenters Increasing Electric Bills for American Households?

https://newsletter.semianalysis.com/p/are-ai-datacenters-increasing-electric
2•2bluesc•19m ago•1 comments

Tell HN: Gemini 3.1 Pro may be responding to other users' prompts

3•Orochikaku•20m ago•0 comments

Show HN: ScopeGate – Granular permission gateway for AI agents (MCP, open-core)

https://scopegate.dev
1•jetbootsmaker•20m ago•0 comments

What Happened to Agent Frameworks?

https://twitter.com/tonykipkemboi/status/2028564120338063859
1•tonykipkemboi•20m ago•1 comments

Show HN: PTEcorepractice – Free PTE Core Practice with Instant AI Scoring for PR

https://ptecorepractice.com
1•zzx•20m ago•0 comments