frontpage.
newsnewestaskshowjobs

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•1y 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•1y 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•1y 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•1y 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.

Notes: Principles of Neural Design

https://act65com.wordpress.com/2018/08/13/notes-principles-of-neural-design/
1•Kotlopou•47s ago•0 comments

Token Leaderboards

https://www.didon.app/blog/ai-token-leaderboards-employee-usage-tracking
2•babakzy•2m ago•0 comments

EU top court dismisses Google fight against record €4B EU antitrust fine

https://www.reuters.com/world/eu-top-court-dismisses-google-fight-against-record-41-billion-eu-an...
1•bontoJR•5m ago•0 comments

Agents.md is lying to your agent – and nothing checks it

https://hunch-pi.vercel.app/blog/post?slug=agents-md-is-lying-to-your-agent
1•huchdave•5m ago•0 comments

Google Reader was building the wrong future

https://buttondown.com/blog/google-reader
2•maguay•8m ago•0 comments

The Age of Personalized Hardware Is Coming

https://geastack.com/blog-the-age-of-personalized-hardware-is-coming
2•arbayi•12m ago•0 comments

Books, Highlights and Progress on Every E-Reader: BookFusion for KOReader

https://www.blog.bookfusion.com/your-books-highlights-progress-onevery-e-reader-bookfusion-for-ko...
2•skillachie•13m ago•0 comments

Synthetic Customers Earn Their Stripes

https://www.bain.com/insights/synthetic-customers-earn-their-stripes/
2•fzliu•13m ago•0 comments

Show HN: MyWritingTwin: an AI Writing Profile that makes LLMs sound like you

https://www.mywritingtwin.com
3•writingdna•24m ago•1 comments

Spent EV Batteries Get Second Life as Higher-Performance Battery Material

https://today.ucsd.edu/story/spent-ev-batteries-get-second-life-as-higher-performance-battery-mat...
3•giuliomagnifico•26m ago•0 comments

EXo Platform 7.2: Native AI Powering a Unified and Intelligent Digital Workplace

https://www.exoplatform.com/blog/exo-platform-7-2-ai-powered-unified-digital-workplace/
3•jaouanebrahim•27m ago•1 comments

A bug I ran into when using Java Modules

https://old.reddit.com/r/java/comments/1ul2wiz/a_bug_i_ran_into_when_using_java_modules_plus/
2•Tomte•27m ago•0 comments

Word Count for Blog Posts: How Long Should Yours Be?

https://fastwordcount.com/blog/real-time-word-counter-boost-your-writing-efficiency/
1•rajkverma123•32m ago•2 comments

Grasse and the London Connection (2025)

https://www.englishmaningrasse.com/post/grasse-and-the-london-connection
1•zeristor•35m ago•0 comments

A 'new way of thinking' boosted math proficiency in an East Palo Alto school

https://www.paloaltoonline.com/east-palo-alto/2026/07/01/a-new-way-of-thinking-boosted-math-profi...
6•hbarka•37m ago•0 comments

Pasqal exceeds 1k Atoms in Quantum Processor

https://www.pasqal.com/newsroom/pasqal-exceeds-1000-atoms-in-quantum-processor/
2•fofoz•40m ago•0 comments

Evaluation order and nontermination in query languages

https://www.rntz.net/post/2026-06-11-datalog-nontermination.html
2•luu•46m ago•0 comments

Show HN: Noter – AI agent dashboard for monitoring coding harnesses locally

https://noterai.tech
1•carlobizzaro•46m ago•0 comments

Show HN: Deterministic Simulation Testing

https://workers.io/blog/deterministic-simulation-testing/
1•chaitanyya•48m ago•0 comments

The Download: Anthropic Launches Claude Science, and California's Carbon Manure

https://www.technologyreview.com/2026/07/01/1139996/the-download-anthropic-claude-science-califor...
2•joozio•52m ago•0 comments

A Machine-Verified Proof of a Quantum-Optimization Conjecture

https://arxiv.org/abs/2606.29687
3•ilaysat•55m ago•0 comments

AgentOS

https://agentos-sdk.dev/
1•handfuloflight•55m ago•1 comments

I think it's still important to understand the code that our agents write

https://twitter.com/geoffreylitt/status/2072522251300409556
4•tosh•58m ago•0 comments

Let's Go Kill the Internet

https://nymag.com/intelligencer/article/doublespeed-tech-founder-creating-an-army-of-ai-influence...
3•Michelangelo11•58m ago•0 comments

MarketFish – Simulate a market with 128 AI consumers before you launch

https://github.com/Key-wxh/market-fish
6•a280887763•1h ago•0 comments

Text AI watermarks will always be trivial to remove

https://www.seangoedecke.com/text-ai-watermarks/
2•ingve•1h ago•0 comments

Show HN: Scalable AI Management Platform

https://github.com/metadist/synaplan/
1•metaralf•1h ago•0 comments

The gauge broke: devs felt 20% faster with AI, measured 19% slower

https://intrepidkarthi.com/writing/the-gauge-broke/
61•intrepidkarthi•1h ago•62 comments

BioShocking AI: "Gaming" the AI Browser and Escaping Its Guardrails

https://layerxsecurity.com/blog/bioshocking-ai-gaming-the-ai-browser-and-escaping-its-guardrails/
1•croes•1h ago•0 comments

Horsewood (2 July 2026) We Tried It My Honest ReviewS

https://finance.yahoo.com/sectors/healthcare/articles/horsewood-urgent-report-2026-horse-19110038...
3•Gafyhanu•1h ago•0 comments