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

Show HN: AI Lint – Teach coding agents your team's standards, not just syntax

1•keepamovin•2m ago•0 comments

Ptolemaic Code seems functional but is based on a fundamentally incorrect model

https://tldr.nettime.org/@dk/115883067614348534
1•AndrewDucker•3m ago•0 comments

Show HN: 3 months cloning Typefully with Claude Code – here's what I learned

1•yeeyang•5m ago•0 comments

Build with Gemini 3 Flash, frontier intelligence that scales with you

https://blog.google/innovation-and-ai/technology/developers-tools/build-with-gemini-3-flash/
2•nnx•11m ago•0 comments

Chess engine, pt. 6: Neural-net evaluation

https://www.dogeystamp.com/chess6/
1•luu•15m ago•0 comments

The Signalflow concepts to learn, for easier charts, alerts

https://martincapodici.com/2026/01/24/the-signalflow-concepts-to-learn-for-easier-charts-alerts-a...
1•mcapodici•19m ago•0 comments

On Programming with Agents

https://zed.dev/blog/on-programming-with-agents
1•saurabh•21m ago•0 comments

Show HN: Orbit – Track "zombie loops" and cost-per-feature in AI agents

https://withorbit.io
1•harshit19932703•23m ago•0 comments

Nix Scripts

https://github.com/QuackHack-McBlindy/dotfiles
1•quackhack•24m ago•0 comments

Data Center Debate, with Philip Johnston (CEO of Starcloud) [video]

https://www.youtube.com/watch?v=0wBFNVEOlnU
1•T-A•25m ago•0 comments

Pigouvian Tax

https://en.wikipedia.org/wiki/Pigouvian_tax
1•nomilk•27m ago•0 comments

What's so special about the find of a Roman panther?

https://www.bbc.co.uk/news/articles/c17zp8pl0pjo
2•zeristor•35m ago•0 comments

A possible future architecture for decoupled GUIs

1•powerwordtree•38m ago•0 comments

Proptest: Property-based testing for Rust (inspired by Hypothesis)

https://github.com/proptest-rs/proptest
1•ThierryBuilds•38m ago•0 comments

A reference layout for Modular Monoliths in TypeScript

https://gist.github.com/ewaldbenes/a7879a187cedb47ed9744ad2929e5d79
1•ebenes•44m ago•0 comments

A self-hosted collaborative viewer for pathology slides (Rust and WebGL2)

https://github.com/PABannier/PathCollab
2•el_pa_b•46m ago•0 comments

NIST is rethinking its role in analyzing software vulnerabilities

https://www.cybersecuritydive.com/news/nist-cve-vulnerability-analysis-nvd-review/810300/
2•milkglass•46m ago•0 comments

On the Tragedy of "The Lost Physics Soul" and the Leap to Structure

https://old.reddit.com/r/prequantumcomputing/comments/1qip5xr/on_the_tragedy_of_the_lost_physics_...
1•bkaminsky•48m ago•0 comments

ast-grep: A CLI tool for code structural search, lint and rewriting

https://github.com/ast-grep/ast-grep
1•aragonite•49m ago•0 comments

Creating a Multi-Agent Tool

https://openagents.org/blog/posts/2026-01-10-walkthrough-creating-a-multi-agent-tool-with
1•snasan•49m ago•1 comments

Show HN: Gmn – A lightweight Gemini CLI in Go (68x faster startup)

https://github.com/tomohiro-owada/gmn
1•abalol•49m ago•0 comments

Garnet: High-performance Redis alternative from Microsoft

https://microsoft.github.io/garnet/
1•wiradikusuma•50m ago•0 comments

Making changing assumptions explicit during development

1•Tobiahao•53m ago•1 comments

I use AI DevKit to develop AI DevKit features

https://codeaholicguy.com/2026/01/24/i-use-ai-devkit-to-develop-ai-devkit-features/
1•hoangnnguyen•53m ago•0 comments

India offloads US bonds, piles up gold in pivot away from dollar assets

https://www.hindustantimes.com/business/india-offloads-us-bonds-piles-up-gold-in-pivot-away-from-...
4•koolhead17•58m ago•0 comments

Not Moaning about AI

https://gilest.org/notes/2026/not-moaning-ai/
1•mindracer•1h ago•0 comments

How Debt Bankrupted the British Empire, and Why America Is Walking the Same Path

https://nitishastra.substack.com/p/how-debt-bankrupted-the-british-empire
4•thisislife2•1h ago•0 comments

Couple Receive $200k Settlement After 'Pungent' Indian Food Complaint

https://www.nytimes.com/2026/01/23/us/palak-paneer-indian-food-racism-settlement.html
1•vinni2•1h ago•0 comments

Modetc: Move your dotfiles from kernel space

https://maxwell.eurofusion.eu/git/rnhmjoj/modetc
2•todsacerdoti•1h ago•0 comments

Gold and Silver Signal the End of American Financial Dominance

https://www.jezebel.com/gold-and-silver-signal-the-end-of-american-financial-dominance
2•thomassmith65•1h ago•1 comments