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.

Forge 4D – a native runtime for building apps without the browser stack

https://codeberg.org/Artanidos/Forge4D
1•artanidos•8s ago•1 comments

Anthropic's Claude Code saved my startup $250k in 9 days

https://www.afr.com/technology/how-anthropic-s-claude-code-saved-my-start-up-250-000-in-9-days-20...
1•cc190305•9s ago•0 comments

Show HN: I Was Here – Draw on street panoramas, others can find your drawings

https://washere.live
1•mrktsm__•48s ago•0 comments

Vibe Coding Is the New Slot Machine

https://www.ssp.sh/brain/generative-ai-and-its-addiction/
2•articsputnik•1m ago•0 comments

Show HN: Tokf – Stop wasting LLM context on verbose build output

https://github.com/mpecan/tokf
1•risethagain•1m ago•0 comments

Proximity Chat for AI Agents

https://github.com/R0mainBatlle/claw-agora
1•romain_batlle•1m ago•1 comments

The 1979 Design Choice Breaking AI Workloads

https://www.cerebrium.ai/blog/rethinking-container-image-distribution-to-eliminate-cold-starts
1•za_mike157•1m ago•0 comments

Show HN: I built a CLI that builds a knowledge graph from your code using LLMs

https://github.com/gzoonet/cortex
1•gzoo•2m ago•0 comments

Show HN: I Replaced MyFitnessPal and Other Apps with a Single MCP Server

https://medium.com/@akutishevsky/how-i-replaced-myfitnesspal-and-other-apps-with-a-single-mcp-ser...
1•ktshvsk•4m ago•0 comments

DARPA's new X-76 Experimental Plane

https://www.darpa.mil/news/2026/darpa-new-x-76-speed-of-jet-freedom-of-helicopter
2•newer_vienna•6m ago•0 comments

Lindsey Graham on US war on Iran:'We're going to make a tonne of money'

https://www.aljazeera.com/news/2026/3/9/we-are-going-make-a-tonne-of-money-us-senator-graham-on-u...
2•inaros•6m ago•0 comments

Seccomp – Unsafe at any speed (2022)

https://blog.habets.se/2022/03/seccomp-unsafe-at-any-speed.html
1•lolpython•6m ago•0 comments

Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents

1•filipbalucha•7m ago•0 comments

Complaining Is the Mind Killer

https://investing101.substack.com/p/complaining-is-the-mind-killer
2•AnhTho_FR•7m ago•0 comments

I don't know Apple's endgame for the Fn/Globe key–or if Apple does

https://aresluna.org/fn/
2•tambourine_man•7m ago•0 comments

Two-Key Writes: Preventing Accidental Autonomy in AI Systems

https://heavythoughtcloud.com/knowledge/two-key-writes-in-ai-systems
2•ryan-s•7m ago•0 comments

The purpose of Continuous Integration is to fail

https://blog.nix-ci.com/post/2026-02-05_the-purpose-of-ci-is-to-fail
2•Norfair•8m ago•0 comments

Anthropic Sues U.S. Defense Department, Pete Hegseth for Targeting the Company

https://www.wsj.com/politics/national-security/anthropic-sues-trump-administration-for-targeting-...
4•dcgudeman•8m ago•0 comments

Online LTL Toolset

https://spot.lre.epita.fr/app/
1•todsacerdoti•8m ago•0 comments

Intelligence: Russian state hackers targeting Dutch Signal and WhatsApp accounts

https://nltimes.nl/2026/03/09/intelligence-confirms-russian-state-hackers-targeting-dutch-signal-...
1•giuliomagnifico•9m ago•1 comments

What I Always Wanted to Know about Second Class Values

https://dl.acm.org/doi/epdf/10.1145/3759427.3760373
2•todsacerdoti•11m ago•0 comments

Open-source AI coding agent skill that finds and fixes infra security misconfigs

https://github.com/coguardio/misconfiguration-detection-skill
2•AlbertHeinle•11m ago•1 comments

Anthropic investors grow frustrated with CEO after feds ban AI startup

https://nypost.com/2026/03/04/business/anthropic-investors-urge-truce-with-pentagon-as-lockheed-m...
11•1vuio0pswjnm7•13m ago•1 comments

TCS had a perfect security score. Then M&S and JLR were breached

https://counterpartywatch.substack.com/p/tcs-had-a-perfect-security-score
4•kseniamorph•15m ago•1 comments

Show HN: I'm 21 and I Just Launched a Website Game

https://www.scalify.ai
2•josh-ternyak•15m ago•0 comments

Decoding Your Vehicle Identification Number

https://crewchief.cc/blog/decoding-your-vin
2•meandave•16m ago•0 comments

Show HN: Execute local prompts in SSH remote shells

https://docs.promptcmd.sh/integrations/ssh
2•tgalal•16m ago•1 comments

Show HN: I built a harness that blocks AI from building until ambiguity < 0.2

https://github.com/Q00/ouroboros
1•q00•16m ago•0 comments

AI Didn't Destroy Your Company, Your Processes Did

https://linuxjedi.co.uk/ai-didnt-destroy-your-company-your-processes-did/
5•speckx•17m ago•1 comments

JSLinux Now Supports x86_64

https://bellard.org/jslinux/
2•TechTechTech•17m ago•0 comments