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

Health NZ staff told to stop using ChatGPT to write clinical notes

https://www.rnz.co.nz/news/national/590645/health-nz-staff-told-to-stop-using-chatgpt-to-write-cl...
3•billybuckwheat•36s ago•0 comments

Specula: A framework for finding deep bugs in system code using TLA+

https://github.com/specula-org/Specula
1•matt_d•1m ago•0 comments

Nonfiction Publishing, Under Threat, Is More Important

https://newrepublic.com/article/207659/non-fiction-publishing-threat-important-ever
1•Hooke•2m ago•0 comments

Show HN: Text2troff – automatically converts plain text to TROFF format

https://github.com/jazzfan2/text2troff
1•robtoscani•2m ago•0 comments

Silence is the KPI: agents that don't talk

https://diegodella1.github.io/chango-daily/2026/03/03/silence-is-the-kpi-agents-that-do-not-talk/
1•changobot_dg•3m ago•0 comments

China is mass-producing hypersonic missiles for $99,000

https://kdwalmsley.substack.com/p/on-sale-now-china-is-mass-producing
1•zdw•3m ago•0 comments

RedSwarm Adversarial AI security scanner, one file, zero deps

https://github.com/beee003/redswarm
1•bee003•4m ago•1 comments

UK bans crypto donations to political parties in bid to curb foreign influence

https://apnews.com/article/uk-political-donations-cryptocurrency-ban-4deae8e71d664a042363fa79d617...
1•toomuchtodo•4m ago•0 comments

FairPhone: Industry First Nature Report

https://www.fairphone.com/stories/we-just-released-the-industrys-first-ever-nature-report
1•kruffalon•5m ago•1 comments

A lawyer won Anthropic's hackathon – what everyone missed

https://hadleylab.org/blogs/2026-03-22-the-lawyer-who-won/
1•idrdex•5m ago•1 comments

Creating Your First React Component Is Easy

https://www.youtube.com/watch?v=lVzYw35oRrk
1•stormsidali2001•6m ago•1 comments

Moon: The Lonely Life of a Man on the Moon

https://reactormag.com/moon-the-lonely-life-of-a-man-on-the-moon/
1•mindracer•6m ago•0 comments

Supreme Court rules ISPs aren't liable for subscribers' music piracy

https://www.engadget.com/entertainment/streaming/supreme-court-rules-isps-arent-liable-for-subscr...
2•zdw•7m ago•1 comments

Show HN: Whorl – Fingerprinting LLMs as horrible password generators

http://bountyplz.xyz/ai,/security/2026/03/15/Model-Fingerprinting-With-Whorl.html
1•tehryanx•8m ago•0 comments

Meta Lays Off 700 Employees, While Rewarding Top Executives

https://www.nytimes.com/2026/03/25/technology/meta-layoffs-ai-executives.html
1•nickvec•9m ago•2 comments

Sculpting Code

https://olshansky.info/posts/2026-03-25-sculpting-code
1•Olshansky•12m ago•0 comments

Daniel Stenberg – Emails

https://daniel.haxx.se/email/
1•leephillips•13m ago•0 comments

Joycraft: Upgrade your Claude Code harness

https://github.com/maksutovic/joycraft
1•max_maksutovic•15m ago•0 comments

Supreme Court Wipes Out Record Labels' $1B Piracy Judgment Against Cox

https://torrentfreak.com/supreme-court-wipes-out-record-labels-1-billion-piracy-judgment-against-...
5•nobody9999•18m ago•1 comments

How to make good lecture slides with AI assistance

https://alexanderhoyle.com/posts/ai-slide-gen.html
1•ahoho•19m ago•0 comments

Marco Arment did something awesome

https://www.natemeyvis.com/marco-arment-did-something-awesome/
1•speckx•19m ago•0 comments

Strong Customer Authentication

https://stripe.com/en-nl/guides/strong-customer-authentication
1•mooreds•21m ago•0 comments

Cella dev journey, a 3D space game in Rust

https://cellagame.com/uptospeed/
1•stldev•21m ago•1 comments

Tired of AI When will this era end?

1•s_u_d_o•22m ago•0 comments

On Claude Code

https://thoughtfractal.pages.dev/on-claude-code/
1•love2read•23m ago•0 comments

All non-government Claude services below two nines of uptime in March 2026

https://status.claude.com/uptime/yyzkbfz2thpt
2•nickvec•25m ago•0 comments

Bernie Sanders and AOC introduce bill to pause building of new datacenters

https://www.theguardian.com/us-news/2026/mar/25/datacenters-bernie-sanders-aoc
5•freediddy•26m ago•0 comments

Interactive web pages. Is this a real defense against AI mode predation?

https://www.fachords.com/guitar-scale/
1•giancaIta•26m ago•0 comments

Chat Control: How Governments and Tech Lobby Try to Overturn EU Parliament

https://www.patrick-breyer.de/en/the-battle-over-chat-control-how-eu-governments-and-the-tech-lob...
5•vrganj•27m ago•0 comments

I installed Fedora and accidentally created a haunted house

https://dnsauve.dev/blog/fedora-haunted-house/
1•dengsauve•29m ago•0 comments