frontpage.
newsnewestaskshowjobs

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.

Import PST file to Office 365

https://www.mailsdaddy.com/pst-to-office-365-migration-tool/
1•somit0•2m ago•0 comments

Show HN: Agent-Otel-Kit – OTel Dashboards for Claude Code, Codex and Gemini CLI

https://github.com/s3onghyun/agent-otel-kit
1•s3onghyun•2m ago•0 comments

Show HN: Vindle – Wordle for Cars

https://vindle.app/
1•cachebag•5m ago•0 comments

Show HN: OpenButterfly – Tracking the environmental impact of the AI ecosystem

https://openbutterfly.com
1•ravipatib•5m ago•0 comments

Did the Apollo Guidance Computer use 60% of the ICs in 1963?

https://retrocomputing.stackexchange.com/questions/12158/did-the-apollo-guidance-computer-really-...
1•Skyfall106•6m ago•0 comments

Show HN: New Book

https://github.com/metereindustries/qeg
1•metereindustrie•7m ago•0 comments

HS 9th Grade ELA Assignment Turned into philosophical rambling

https://liamis.dev/blogs/CaptionRambling/
1•ForgottenMail•10m ago•0 comments

Google AI Ultra Subscription Not Worth It

https://www.reddit.com/r/google_antigravity/comments/1xx9nl3/google_ai_ultra_subscription_not_wor...
3•behnamoh•13m ago•0 comments

Jensen Huang's downfall will accelerate US-China 'great decoupling'

https://www.channelnewsasia.com/commentary/nvidia-jensen-huang-affair-us-china-ai-tech-decoupling...
1•Markoff•13m ago•0 comments

RISC-V Matrix Extensions

https://fprox.substack.com/p/risc-v-matrix-extensions
1•hasheddan•18m ago•0 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
3•artooro•19m ago•0 comments

Show HN: A benchmark that diffs the whole database after an AI agent's task

https://github.com/shubhamjoshipromail-svg/software-world-model
1•shubhamjoshipro•23m ago•0 comments

Ask HN: How to visually edit vibe coded websites?

1•keepitverysimpl•23m ago•1 comments

Why did base64 win against uuencode? (2023)

https://retrocomputing.stackexchange.com/questions/3019/why-did-base64-win-against-uuencode
1•zenincognito•35m ago•1 comments

Stop Filming in Log

https://digitalfilms.wordpress.com/2026/11/15/stop-filming-in-log/
2•dabinat•35m ago•0 comments

OpenQuantum's DIY Open-Source Magneto-Optical Atomic Trap

https://www.diyphysics.com/2023/11/10/openquantums-diy-open-source-magneto-optical-atomic-trap/
1•o4c•39m ago•0 comments

Microsoft outage based phishing live now

https://ravenmail.io/blog/microsoft-365-outage-phishing-lure
2•abishekr•40m ago•0 comments

Artex.sh

https://www.artex.sh
1•iLuddite•43m ago•0 comments

An update on Cursor's recent security incident

https://cursor.com/blog/security-incident-update
1•nreece•44m ago•0 comments

Do Firms Know What Workers Want? [pdf]

https://www.econtribute.de/RePEc/ajk/ajkdps/ECONtribute_443_2026.pdf
1•rohanm93•49m ago•0 comments

Artificial Intelligence in Neuromuscular Diseases

https://link.springer.com/article/10.1007/s40120-026-01017-8
1•measurablefunc•49m ago•0 comments

Show HN: Shot Ease – Screen Capture full pages

https://chromewebstore.google.com/detail/shot-ease-screen-capture/cejbjpbkachlmgbphckaikicmnpmfjdn
1•lucakk•51m ago•0 comments

The Nefarious Plan of vm2

https://nefariousplan.com/posts/the-nefarious-plan-of-vm2
1•tsavo42•52m ago•0 comments

Requests for Hardwares

https://blog.greg.technology/2026/11/14/requests-for-hardwares.html
1•gregsadetsky•58m ago•0 comments

Effect of Process and Geometric Parameters on Residual Distortion of Ti-6Al-4V

https://www.sciencedirect.com/science/article/pii/S2950431724000601
1•num42•1h ago•0 comments

US and Russia to oppose talks on limiting autonomous weapons

https://www.reuters.com/world/us-russia-oppose-talks-limiting-autonomous-weapons-2026-11-16/
3•geox•1h ago•0 comments

Pyr.js: Python and R in HTML pages, with one script tag

https://www.r-bloggers.com/2026/11/pyr-js-python-and-r-in-html-pages-with-one-script-tag/
1•xnx•1h ago•0 comments

Global Chip Supply After Jensen Huang's Fall

https://medium.com/@klay_79514/global-chip-supply-after-jensen-huangs-fall-1ba96ba609b0
2•klay_moon•1h ago•1 comments

A Local-First Agent for Private Knowledge Work

https://www.perplexity.ai/hub/blog/a-local-first-agent-for-private-and-cost-effective-knowledge-work
1•thunderbong•1h ago•0 comments

Nvidia's Days as an Open Checkbook for the AI Economy Are Numbered

https://www.wsj.com/tech/ai/nvidias-days-as-an-open-checkbook-for-the-ai-economy-are-numbered-90c...
5•mfiguiere•1h ago•0 comments