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•7mo 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•7mo 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•7mo 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•7mo 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: Nudge – Inject rules into agent context

https://github.com/attunehq/nudge
1•ilikebits•59s ago•0 comments

OpenAI has acquired the health-care technology startup Torch

https://www.cnbc.com/2026/01/12/open-ai-torch-health-care-technology.html
1•shelfchair•4m ago•0 comments

Google removes AI health summaries after investigation finds dangerous flaws

https://arstechnica.com/ai/2026/01/google-removes-some-ai-health-summaries-after-investigation-fi...
2•barishnamazov•5m ago•0 comments

Non-Essential French Embassy Staff Have Left Iran

https://www.barrons.com/news/non-essential-french-embassy-staff-have-left-iran-sources-d84d1f51
5•mhb•7m ago•0 comments

A deep dive on agent sandboxes

https://pierce.dev/notes/a-deep-dive-on-agent-sandboxes
1•icyfox•7m ago•0 comments

Republican introduces bill seeking to make Greenland 51st state

https://thehill.com/homenews/house/5685118-fine-introduces-greenland-bill/
3•zqna•13m ago•2 comments

The "Bermuda Triangle" and the Growing Risk in the Insurance Markets

https://natlawreview.com/article/bermuda-triangle-and-growing-risk-insurance-markets
1•petethomas•16m ago•0 comments

GoFundMe Ignores Rules Hosting Legal Fund for ICE Agent Who Killed Renee Good

https://www.wired.com/story/gofundme-ice-jonathan-ross-renee-good-fundraiser/
6•cdrnsf•17m ago•1 comments

Map Your API Landscape to Prevent Agentic AI Disaster

https://thenewstack.io/map-your-api-landscape-to-prevent-agentic-ai-disaster/
2•chhum•18m ago•0 comments

GitHub not showing that apps "act on your behalf" when only logging in

https://github.blog/changelog/2026-01-12-selectively-showing-act-on-your-behalf-warning-for-githu...
2•gregsadetsky•20m ago•0 comments

YAML? That's Norway Problem

https://lab174.com/blog/202601-yaml-norway/
1•thes1lv3r•20m ago•0 comments

China Just Built Its Own Time System for the Moon

https://gizmodo.com/china-just-built-its-own-time-system-for-the-moon-2000708991
1•hunglee2•20m ago•0 comments

Mars's big impact on Earth's climate: How the red planet's pull shapes ice ages

https://phys.org/news/2026-01-tiny-mars-big-impact-earth.html
1•bikenaga•23m ago•1 comments

Ask HN: Speculate About a Hypothetical Cyber Exploit That Would Leverage AI

2•burnerToBetOut•24m ago•0 comments

Data-Dividend Calculator

https://delightful-maamoul-98e039.netlify.app
1•KillswitchAI•24m ago•0 comments

I built an ingestion engine because I hate mundane tasks

2•scannyai•25m ago•0 comments

Dialectics for Artificial Intelligence

https://arxiv.org/abs/2512.17373
1•xiaoniu•25m ago•0 comments

Even Linus Torvalds is vibe coding now

https://www.zdnet.com/article/linus-torvalds-vibe-coding-ai/
1•CrankyBear•25m ago•1 comments

Do you know how much money social apps make from your time

https://www.urtheproduct.com
4•ClipNoteBook•27m ago•2 comments

Danish dev delights kid by turning floppy drive into easy TV remote

https://www.theregister.com/2026/01/12/danish_dev_floppy_drive_remote/
1•defrost•28m ago•2 comments

Transactional AI: Saga Pattern for Reliable AI Agent Workflows (v0.2)

https://github.com/Grafikui/Transactional-ai
2•grafikui•28m ago•1 comments

Wine 11.0 Planned for Release Tomorrow with NTSync Support, Better WoW64

https://www.phoronix.com/news/Wine-11.0-Tomorrow
2•mikece•28m ago•0 comments

99% of Heart Attacks and Strokes Linked to 4 Risk Factors

https://www.sciencealert.com/huge-study-links-99-of-heart-attacks-and-strokes-with-4-risk-factors
2•Gaishan•29m ago•0 comments

Ask HN: Are you using agents for refactorings?

1•suralind•31m ago•0 comments

Green Corn Ceremony

https://encyclopediaofalabama.org/article/green-corn-ceremony/
1•foster_nyman•31m ago•0 comments

Climate misinformation is threatening Canada's national security

https://thenarwhal.ca/climate-misinformation-national-security/
3•Teever•35m ago•0 comments

Workflow Description Language (WDL) 1.3

https://openwdl.org/wdl/bioinformatics/workflows/announcing-wdl-1-3-0/
1•azhenley•37m ago•0 comments

What's on HTTP?

https://whatsonhttp.com/
1•elixx•39m ago•0 comments

Seniority Is Clarity Not Cleverness

https://dontbreakprod.com/posts/seniority-is-clarity-not-cleverness
3•dorkrawk•41m ago•1 comments

I Taught Myself to Code on a Cracked Android Phone. Now I Can't Get Hired

https://www.rly0nheart.com/posts/life/i-taught-myself-to-code-on-a-cracked-android-phone-now-i-ca...
19•boyter•48m ago•4 comments