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

Quantizing Tangent Frames

https://zeux.io/2026/04/30/quantizing-tangent-frames/
1•ibobev•46s ago•0 comments

Building an Open Source 7MB AI Terminal with Agents and Code Editor (Rust/Tauri)

https://github.com/crynta/terax-ai
1•crynta•2m ago•1 comments

The reason that everybody use LLMs [video]

https://www.youtube.com/watch?v=xE9W9Ghe4Jk
1•modinfo•2m ago•0 comments

Gnome Surface next-generation AI desktop platform built with GirCore-SkiaSharp

https://github.com/GnomeMaui/surface
1•czirok•3m ago•0 comments

Sumud flotilla ships released from Greek detention

https://www.marinetraffic.com/en/ais/home/shipid:85582/zoom:10
1•burnt-resistor•5m ago•1 comments

Nobody cares about what you do in the "Shadows"

https://saulala.discourse.group/t/nobody-cares-about-what-you-do-in-the-shadows/83
2•debesyla•7m ago•0 comments

CPanel's 30-Day Security Storm

1•panelica•7m ago•0 comments

Microsoft document spells out the company's buyout offer

https://www.businessinsider.com/microsoft-internal-document-shows-buyout-offers-to-us-employees-2...
1•the1plummie•8m ago•0 comments

SpaceXAI prepares Grok Build desktop app to rival OpenAI Codex

https://www.testingcatalog.com/spacexai-prepares-grok-build-desktop-app-to-rival-openai-codex/
1•mirzap•9m ago•0 comments

Martin van den Brink – Engineer and Architect of lithography systems at ASML

https://www.youtube.com/watch?v=XK84TlYTv5k
2•pillars•9m ago•0 comments

The Roadmap to Mastering Tool Calling in AI Agents

https://machinelearningmastery.com/the-roadmap-to-mastering-tool-calling-in-ai-agents/
1•dcu•10m ago•0 comments

Show HN: Turn E2E tests into observability signals

https://faultsense.com
1•mitchm•11m ago•1 comments

Supportson-AI support widget with video calls, built by an AI co-founder($29/mo)

https://supportson.com
1•peercast•11m ago•1 comments

Pentagon Tests Ingenious Plan to Protect Coasts from Hurricanes–and It's Working

https://gizmodo.com/pentagon-think-tank-just-came-up-with-an-ingenious-plan-to-protect-coasts-fro...
1•giuliomagnifico•14m ago•0 comments

Renovate with Figma

https://www.shapes.gg/renovate-with-figma/
1•GjermundG•16m ago•1 comments

Scaling to Global: Full Bilingual Support Added to Croisée

https://www.indiehackers.com/post/scaling-to-global-full-bilingual-support-added-to-crois-e-La2wb...
1•coisee•17m ago•0 comments

Fob – a local continuity layer for Claude, Codex, ChatGPT and Gemini

https://fob.sh
2•nharing•20m ago•0 comments

Eisenstein– exact hexagonal arithmetic for Rust (zero drift after 10k rotations)

https://superinstance.ai/demos
3•SuperInstance•20m ago•0 comments

Getting peak TOPS on a Ryzen AI 7 350 NPU

https://destevez.net/2026/05/getting-peak-tops-on-a-ryzen-ai-7-350-npu/
1•tverbeure•21m ago•0 comments

Focus Areas for the Anthropic Institute

https://www.anthropic.com/research/anthropic-institute-agenda
1•nedruod•27m ago•0 comments

Wipeout in Browser

https://hexgl.bkcore.com/#press
2•lovegrenoble•28m ago•0 comments

I lost track of which Claude Code tab needed me, so I built this

https://github.com/dgr8akki/claude-tab-watcher
2•dgr8akki•28m ago•0 comments

Blink – AI Assistant

https://blink-oi.vercel.app
1•Pascal1997•29m ago•0 comments

The Programmer After AI

https://gist.github.com/tamnd/11665e492d7a3b91ce54e26ecbd97248
1•tamnd•30m ago•0 comments

Stop MitM on the first SSH connection, on any VPS or cloud provider

https://www.joachimschipper.nl/Stop%20MITM%20on%20the%20first%20SSH%20connection,%20on%20any%20VP...
1•JoachimSchipper•31m ago•0 comments

Aube: Fast Node.js package manager that works with your existing lockfiles

https://aube.en.dev/
1•thunderbong•32m ago•0 comments

Western Horizon Technologies TI 99/4a and Geneve Archive

https://ftp.whtech.com/
2•oldnetguy•32m ago•0 comments

Creativity and AI

https://roo.se/en/blog/creativity-and-ai/
1•rroose•33m ago•1 comments

Reviving Teletext for Ham Radio Hack the airwaves with some tech of the 1980s

https://spectrum.ieee.org/reviving-teletext-for-ham-radio
2•oldnetguy•35m ago•0 comments

An Introduction to Meshtastic

https://meshtastic.org/docs/introduction/
2•ColinWright•35m ago•0 comments