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.

Greenest countries eye drilling as fix for Iran crisis

https://www.politico.eu/article/worlds-greenest-countries-eye-drilling-as-fix-for-iran-crisis/
1•leonidasrup•1m ago•0 comments

If this doesn't scream AI bubble is about to burst IDK what does

https://docs.github.com/en/copilot/reference/copilot-billing/models-and-pricing
1•julia-kafarska•2m ago•0 comments

Goodbye Tim Apple – daily.dev Show [video]

https://www.youtube.com/watch?v=XKO67n3xfzM
1•idosh•5m ago•0 comments

What Type of AI Usage?

https://jensrantil.github.io/posts/types-of-ai-implementations/
1•JensRantil•5m ago•1 comments

AI Is Cannibalizing Human Intelligence

https://www.wsj.com/tech/ai/is-ai-smarter-than-humans-cyborg-956e0f0e
1•JeanKage•6m ago•0 comments

$1,605: average annual ad value of a U.S. Google user

https://proton.me/blog/what-is-your-data-worth-to-google
3•muzzy19•9m ago•0 comments

A Field Guide to Bugs

https://www.stephendiehl.com/posts/field_guide_to_bugs/
1•signa11•9m ago•0 comments

Phony whistleblowers, fake journalists and cyber spies

https://www.icij.org/investigations/china-targets/fake-journalists-cyber-spies-china-targets-repo...
1•_tk_•11m ago•0 comments

AI Workflows Need Provider Escape Hatches

https://rawsignal.xyz/posts/ai-workflows-need-provider-escape-hatches/
1•chown•13m ago•0 comments

Comparing SBC prices in 2024 and 2026

https://www.cnx-software.com/2026/04/28/what-a-difference-two-years-make-comparing-sbc-prices-in-...
1•pyprism•13m ago•0 comments

GitHub Copilot code review will start consuming GitHub Actions minutes

https://github.blog/changelog/2026-04-27-github-copilot-code-review-will-start-consuming-github-a...
1•whtsky•15m ago•0 comments

AI prefers resumes written by itself: Self-preferencing in Algorithmic Hiring

https://arxiv.org/abs/2509.00462
2•ytpete•18m ago•1 comments

Notice of Obsolescence

https://thebuild.com/blog/2026/04/27/notice-of-obsolescence/
1•ggaughan•18m ago•0 comments

Donating to Open Source

https://entropicthoughts.com/open-source-donation
1•exiguus•21m ago•0 comments

The era of "malicious compliance" in AI identity is here

https://arielsakin.substack.com/p/the-era-of-malicious-compliance-in
2•asakin•23m ago•0 comments

A Complete History of Quantum Computing (and what comes next)

https://quantumzeitgeist.com/a-complete-history-of-quantum-computing/
1•Nazzareno•25m ago•0 comments

Show HN: Devicons, +1300 logos and icons in React, SVG, and icon format

https://devicons.io/
2•vorillaz•25m ago•0 comments

A Year of Hetzner Auction Data: Where Did All the Servers Go?

https://blog.iodev.org/blog/hetzner-auction-supply-crunch/
2•100ms•28m ago•0 comments

London Met Police investigates officers after using Palantir AI tool

https://www.theguardian.com/uk-news/2026/apr/25/met-police-investigates-hundreds-officers-palanti...
1•lucidplot•28m ago•2 comments

Claud is missing the 2. Sense – Transcribe the web

https://webtranscriber.com/
1•broalkvam•29m ago•1 comments

Show HN: A free crypto trade journal with cycle support and CSV import

https://retired.today/log
1•attendos•30m ago•0 comments

Show HN: Delegare – let AI agents pay safely (x402, AP2 – base/USDC and Stripe)

https://delegare.dev/
1•tpfuetze•31m ago•0 comments

From milliseconds to 26 nanoseconds: how a $20 eBay SFP module beat my NT

https://austinsnerdythings.com/2026/04/26/ptp-osa5401-26-nanoseconds-raspberry-pi/
1•fanf2•34m ago•0 comments

How to run a local coding agent with Gemma 4 and Pi

https://patloeber.com/gemma-4-pi-agent/
1•mariuz•35m ago•0 comments

Top Negotiation Skills

https://www.pon.harvard.edu/daily/negotiation-skills-daily/top-10-negotiation-skills/
1•lucidplot•35m ago•0 comments

Bohu Laser Facility

https://en.wikipedia.org/wiki/Bohu_laser_facility
1•lumax•36m ago•0 comments

I built a WordPress plugin that generates 1000 SEO pages in minutes

https://www.indiehackers.com/post/i-built-a-wordpress-plugin-that-generates-100-seo-pages-in-minu...
1•codefreex•36m ago•0 comments

Trump administration to pay companies to walk away from US offshore wind leases

https://apnews.com/article/trump-offshore-wind-energy-climate-interior-02a1fa04b750809bbe035a7025...
4•geox•39m ago•1 comments

Show HN: The newsroom that runs itself; hiring AI Journalists [TokenToday]

1•gnapapp•41m ago•0 comments

Mitigating Belief Inertia via Active Intervention in Embodied Agents

https://arxiv.org/abs/2604.17252
2•MemTensor•47m ago•1 comments