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.

Training within 10 hours of bedtime measurably hurts recovery

https://tryterra.co/research/best-time-to-workout-for-sleep
1•kyriakosel•4m ago•0 comments

Company Was an American Success Story. Until MAHA Influencers Sank It

https://www.thefp.com/p/this-company-was-an-american-success-until-maha-sank-it
1•rmason•4m ago•0 comments

Trump Order Would Push Banks to Check Clients' Citizenship Status

https://www.wsj.com/finance/regulation/trump-order-would-push-banks-to-check-clients-citizenship-...
1•petethomas•9m ago•0 comments

You Can't Park at 0.1c

https://samirvarma.substack.com/p/you-cant-quietly-park-at-01c
1•qsi•10m ago•0 comments

What are account recovery options with FusionAuth?

https://fusionauth.io/community/forum/topic/3133/what-are-account-recovery-options-with-fusionauth
1•mooreds•15m ago•0 comments

Why "Fast AI" and "Safe AI" Were Never in Conflict

https://www.enkryptai.com/blog/why-fast-ai-and-safe-ai-were-never-actually-in-conflict
1•mooreds•15m ago•0 comments

Etymonline: An Online Etymology Dictionary

https://www.etymonline.com
1•airstrike•17m ago•0 comments

Debunking the job-hopping myth: A Data-Driven Look at Tenure and Turnover [pdf]

https://www.nirsonline.org/wp-content/uploads/2025/09/25-Debunking-Job-Hopping-Myth_FINAL.pdf
2•gmays•19m ago•0 comments

Enterprise AI: Mystery Meat, Kill Zones, Cognitive Surrender, Vibe Bombs

https://kyield.com/insights/newsletter/2026/05/vibe-bombs-cognitive-surrender.html
1•mooreds•19m ago•0 comments

Apple Taps Virtual Avatar Firm Animato's Expertise and Intellectual Property

https://www.macrumors.com/2026/05/19/apple-acquires-animato/
1•mgh2•20m ago•0 comments

Cyoda-Go: The Enterprise Edbms

https://github.com/Cyoda-platform/cyoda-go
1•petethomas•25m ago•0 comments

Alternatives to HN for "tech outside of AI" discussion?

2•summonerOS•25m ago•0 comments

Customizing an LLM for Enterprise Software Engineering

https://arxiv.org/abs/2605.16517
1•azhenley•26m ago•0 comments

Zephex is hosted MCP that gives AI coding editors persistent project context

https://zephex.dev
1•zephex•30m ago•0 comments

Repugnant Economics

https://marginalrevolution.com/marginalrevolution/2026/05/repugnant-economics.html
3•paulpauper•34m ago•0 comments

Show HN: SafeRun – Replay debugging and inline prevention for AI agents

1•Tidianez•34m ago•0 comments

Old Space, New Space: A Commercial Revolution in Innovation?

https://www.nber.org/papers/w35212
1•paulpauper•34m ago•0 comments

Australia and Pax Silica: The Quiet Foundations of a New Western Order?

https://sldinfo.com/2026/05/australia-and-pax-silica-the-quiet-foundations-of-a-new-western-order/
1•Gaishan•35m ago•0 comments

Sen. Cassidy casts deciding vote in legislation to end Iran war [video][40s]

https://www.youtube.com/watch?v=S-h8oM7kGEE
2•Bender•36m ago•0 comments

Vacuum flux has memory too [4]

1•sargstuff•36m ago•0 comments

Meta Begins 8k Global Job Cuts in Asian Hub of Singapore

https://finance.yahoo.com/sectors/technology/articles/meta-begins-8-000-global-004153394.html
3•doppp•39m ago•0 comments

Copyright Office Rejected My Attempt to Copyright a Tweet

https://www.techdirt.com/2014/08/04/copyright-office-rejected-my-attempt-to-copyright-tweet/
2•danhite•44m ago•1 comments

Ember: 365-day audited record of AI models vs. Polymarket, scored by Brier

https://emberfyi.com/
1•emberfyi•45m ago•0 comments

AI video editing is blowing my mind

https://aivideoediting.io/
1•pekingzcc•50m ago•0 comments

Architect of the UK Online Safety Act Calls for Its Complete Repeal

https://prestonbyrne.com/2026/05/19/architect-of-the-uk-online-safety-act-calls-for-its-complete-...
5•iamnothere•51m ago•0 comments

Rendezvous: A serverless, Zoom-like video conferencing web app

https://github.com/predatorray/rendezvous
2•zetaplusae•57m ago•0 comments

Generalization Dynamics of LM Pre-Training

https://jiaxin-wen.github.io/blog/generalization-dynamics
1•gmays•58m ago•0 comments

Iteration

https://blog.viktomas.com/posts/iteration/
1•luca-sctr•59m ago•0 comments

GPU telemetry anomaly: 146W idle draw on A100 (white paper)

https://github.com/mikebains41-debug/ai-gpu-energy-optimizer-/blob/main/WHITEPAPER.md
1•mikebains•1h ago•0 comments

Who Wins the Future: Chips vs. Frontier LLMs

https://medium.com/@vektormemory/who-wins-the-future-chips-vs-frontier-llms-1e8e0ca42641
2•vektormemory•1h ago•1 comments