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

Show HN: A high-performance audio visualizer using Rust, WASM, and React

https://audiofftimage.netlify.app/
1•dmaynard•30s ago•0 comments

Show HN : Building Production MPC Wallets: Architecture, Solana Implementation

https://nethsara.substack.com/p/byowbuild-your-own-wallet-a-field
1•nethsarask•2m ago•0 comments

Show HN: GPTFortress, a 24/7 live-stream playing Dwarf Fortress with GPT-5

https://www.twitch.tv/gptfortress
1•leostera•5m ago•0 comments

AI guardrails stripped from Meta and Google models in minutes

https://www.ft.com/content/5630ed79-a263-41ed-9a1a-321617ae310e
2•thunderbong•5m ago•1 comments

Ship Early, Learn Fast: What 10 Days of User Feedback Taught Me About My App

https://qebapps.statichost.page/devnotes/ship-early-learn-fast/
1•qeb_newsairy•8m ago•0 comments

The Quiet Death of the Senior Individual Contributor

https://medium.com/@yalovoy/the-quiet-death-of-the-senior-individual-contributor-why-staff-engine...
1•zero-ground-445•8m ago•0 comments

Show HN: Riot, a modern multicore actor-based ecosystem for OCaml

https://riot.ml
1•leostera•9m ago•0 comments

Why can't anyone build a decent deployment platform for plain HTML?

https://foliodrop.app
1•jaxxchen•13m ago•1 comments

Frontier Model Training Methodologies

https://djdumpling.github.io/2026/01/31/frontier_training.html
1•xdotli•17m ago•1 comments

Microsoft to Publishers: Don't Block the AI Bots

https://www.adexchanger.com/publishers/microsoft-to-publishers-dont-block-the-ai-bots/
3•SVI•18m ago•0 comments

Zero-knowledge encryption may not stop password theft if servers are hacked

https://techxplore.com/news/2026-02-knowledge-encryption-password-theft-servers.html
1•Ember_Wipe•19m ago•0 comments

AI Making Work Easy for Data Analysts and Founders

https://anallyst.app/
1•Sechele•21m ago•0 comments

Why codex /goal fails on complex workflows: compaction amnesia and context rot

1•shaurya-sethi•22m ago•0 comments

AI Gurus Are Charging Wall Street Banks $25,000 a Day

https://www.bloomberg.com/news/features/2026-05-25/the-ai-trainers-charging-25-000-a-day-to-push-...
3•helsinkiandrew•23m ago•1 comments

Outlines – Structured LLM Outputs

https://dottxt-ai.github.io/outlines/latest/
1•modinfo•23m ago•0 comments

Joi AI is hiring masturbation consultants to test "Daily Guided Masturbation"

https://twitter.com/joi___ai/status/2056518876243149258
1•rjzzleep•25m ago•0 comments

Galaxiana – Dedicate a star in a living 3D galaxy

https://galaxiana.com
1•neribar•30m ago•0 comments

Desktop Monitoring and Notifications for CISA KEV

https://github.com/quantumcore/kev_monitor
1•tt560•33m ago•0 comments

ThriftAttention: Selective Mixed Precision for Long-Context FP4 Attention

https://arxiv.org/abs/2605.23081
2•joesharratt29•34m ago•1 comments

Ferrari Reveals $640k EV Co-Designed by Jony Ive

https://www.macrumors.com/2026/05/25/ferrari-luce-jony-ive-photos/
1•mgh2•35m ago•0 comments

Stealth Firefox that passes every bot detection test

https://github.com/feder-cr/invisible_playwright
2•federcr•36m ago•0 comments

Webwright: A terminal is all you need for web agents

https://microsoft.github.io/Webwright/
2•sorenbs•37m ago•0 comments

Standard WiFi can identify individuals with near-perfect accuracy

https://www.digitaljournal.com/tech-science/privacy-any-wi-fi-can-now-identify-you-with-near-perf...
4•jackson-mcd•38m ago•0 comments

The Pressure

https://daniel.haxx.se/blog/2026/05/26/the-pressure/
3•adunk•39m ago•0 comments

Jazz legend Sonny Rollins dies aged 95

https://www.bbc.co.uk/news/articles/c1e224dwz18o
1•2dvisio•41m ago•0 comments

Show HN: Burn, K8s cost CLI that pulls actual spot prices per instance type

https://github.com/tanrikuluozlem/burn
1•OzlemT•41m ago•0 comments

Accelerating Copy_if Using SIMD

https://loonatick-src.github.io/posts/vectorized-copy-if-analysis/
1•chkmr•42m ago•0 comments

Users have created a tool to fix firmware issues with the Audeze Maxwell 1

https://github.com/kats1123/maxwell-balance-and-firmware-tool
1•ilitirit•44m ago•0 comments

What ClickUp's mass layoff tells us about the future of work

https://techcrunch.com/2026/05/25/what-clickups-mass-layoff-tells-us-about-the-future-of-work/
3•01-_-•45m ago•1 comments

America's schools face a backlash on digital devices

https://apnews.com/article/school-screen-time-technology-edtech-07958fb159c7cfbceb7bfdb37b2bb726
5•01-_-•46m ago•1 comments