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

Mother of one of Elon Musk's sons sues over Grok-generated explicit images

https://www.theguardian.com/technology/2026/jan/15/mother-of-one-of-elon-musks-sons-sues-over-gro...
1•beardyw•2m ago•0 comments

GCRA vs. Leaky / Token Buckets

https://dotat.at/@/2026-01-15-gcra.html
1•enz•7m ago•0 comments

What is Reticulum? – Reticulum Network Stack 1.1.3 documentation

https://reticulum.network/manual/whatis.html
1•qbonnard•9m ago•1 comments

LLDB in 2025

https://jonasdevlieghere.com/post/lldb-2025/
1•ingve•11m ago•0 comments

Show HN: AI agent that joins Google Meet/Zoom to give live product demos

https://www.pipersdr.com/
1•ajabhish•21m ago•0 comments

JavaScript virtual machine with QuickJS running in WASM under Go/JS

https://github.com/aperturerobotics/go-quickjs-wasi-reactor
1•aperturecjs•25m ago•1 comments

Pratfall Effect

https://en.wikipedia.org/wiki/Pratfall_effect
2•rzk•26m ago•0 comments

Uncensored AI for image and video generation

https://www.gocrazyai.com/
1•shotvu•28m ago•0 comments

A guide on how to use beets, a media library manager

https://gist.github.com/DevER-M/a52b363b21093d8d285fb86c4aa098b5
1•DevER-M•33m ago•1 comments

Irrational betting craze signals we're on the cusp of a crash

https://www.thetimes.com/business/companies-markets/article/stocks-ai-crash-imminent-prediction-m...
3•petethomas•34m ago•2 comments

Show HN: BrewBar – a native macOS menubar app to manage Homebrew services

https://github.com/OmkarKirpan/BrewBar
1•omkarkirpan•35m ago•1 comments

MCP for GoDaddy

https://github.com/alpnix/GoDaddy-MCP
1•alpnix•38m ago•0 comments

How to wrangle non-deterministic AI outputs into conventional software? (2025)

https://www.domainlanguage.com/articles/ai-components-deterministic-system/
3•druther•41m ago•1 comments

Building a better Bugbot

https://cursor.com/blog/building-bugbot
8•onurkanbkrc•44m ago•0 comments

Playing daily games at work? Timdle just launched work mode

https://www.timdle.com/work
3•maskinberg•45m ago•0 comments

Ralph wiggum Agentic Coding Frameworks in 2026

https://ralphwiggum.org/blog/agentic-coding-frameworks-guide
1•zlonmask•45m ago•0 comments

Six more AI outfits sign for Wikimedia's fastest APIs

https://www.theregister.com/2026/01/16/wikimedia_25_ai_partner_access/
1•beardyw•46m ago•1 comments

Pi Coding Agent

https://github.com/badlogic/pi-mono/tree/main/packages/coding-agent
1•ttobi•47m ago•0 comments

Ask HN: Share Your Personal Website

1•SRMohitkr•48m ago•0 comments

Our First Press Release: Mentra Releases First Smart Glasses with an App Store

https://mentraglass.com/blogs/blog/our-first-press-release-mentra-releases-first-smart-glasses-wi...
1•_____k•48m ago•0 comments

Chinese AI Developers Say They Can't Beat America Without Better Chips

https://www.wsj.com/tech/ai/china-ai-race-us-chips-9e74b957
2•Brajeshwar•49m ago•0 comments

Local-Only Marstek Venus E Battery Integration with Home Assistant

https://du.nkel.dev/blog/2026-01-11_marstek-battery-homeassistant/
1•Helmut10001•50m ago•0 comments

Decoding Academic Papers with AI: A Practical Guide

https://joshtuddenham.dev/blog/hashmaps/
1•reinhardt•51m ago•1 comments

Meta Horizon Workrooms is being discontinued

https://www.meta.com/en-gb/help/quest/2464765133873078/
1•_____k•52m ago•0 comments

Nobel Institute says Venezuelan leader Machado can't give Peace Prize to Trump

https://apnews.com/article/trump-machado-nobel-peace-prize-c7f47c161edc9b719dea3d0165f32a1f
3•wslh•59m ago•0 comments

Show HN: Convert PNG to STL Free Online Tool

https://pngtostl.xyz
1•niliu123•1h ago•0 comments

Hardware‑Attested Ad Insertion for Encrypted Video

https://www.gojiberries.io/hardware-attested-ad-insertion-for-encrypted-video/
1•neehao•1h ago•0 comments

Histomat of F/OSS: We should reclaim LLMs, not reject them

https://writings.hongminhee.org/2026/01/histomat-foss-llm/
1•todsacerdoti•1h ago•0 comments

Training large language models on narrow tasks can lead to broad misalignment

https://www.nature.com/articles/s41586-025-09937-5
3•thebeardisred•1h ago•0 comments

Hierarchy view now available in GitHub Projects

https://github.blog/changelog/2026-01-15-hierarchy-view-now-available-in-github-projects/
1•fphilipe•1h ago•1 comments