frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Brew Browser – A Native macOS GUI for Homebrew

https://brew-browser.zerologic.com/
1•jonbaer•30s ago•0 comments

Show HN: Inkwash, a watercolor sketching app and explanation

https://johnowhitaker.github.io/inkwash/about
1•Yenrabbit•2m ago•0 comments

The Australian Town Where More Than Half the Population Lives Underground

https://terralocate.com/interesting/coober-pedy-australia-underground-town
1•thunderbong•6m ago•0 comments

Download Free Marketing Software

https://www.coolmarketingsoftware.com/osclass-submitter/
1•bokeke1•7m ago•0 comments

What Should I Build?

1•gooob•12m ago•0 comments

ClawMoat, runtime containment for AI agents after Fable 5

https://clawmoat.com/
1•ildar•13m ago•0 comments

5.3M-year-old deep-sea whale necropolis in the Diamantina Zone

https://www.nature.com/articles/s41586-026-10546-z
3•defrost•15m ago•0 comments

Ask HN: Which cheap Chinese LLM are you using?

2•linzhangrun•16m ago•0 comments

GIER: A Danish computer from 1961 with a role in the modern astronomy

https://arxiv.org/abs/1704.05828
1•andrewstuart•18m ago•0 comments

Lime 2.0 – Zero Human Auth for AI Agents

https://lime.pics
1•MawyxxY•29m ago•1 comments

Brew Browser: A Native macOS GUI for Homebrew

https://github.com/msitarzewski/brew-browser
2•amichail•34m ago•0 comments

Vincent's parents 'never say he's good enough' so he turned to a couple online

https://www.bbc.com/news/articles/cpq3dnr5vlzo
2•breve•37m ago•0 comments

The whirlwind 24 hours that led to export controls on Anthropic

https://www.politico.com/news/2026/06/13/inside-the-whirlwind-24-hours-that-led-the-white-house-t...
5•ls612•39m ago•1 comments

Surface Data vs. Deep Data [video]

https://www.youtube.com/watch?v=vk6lgHjjGp8
1•zetamax•42m ago•0 comments

The Siren Song of Illness

https://www.nybooks.com/articles/2026/06/25/the-siren-song-of-illness-master-of-contradictions-je...
2•t0lo•45m ago•0 comments

The Missing Infrastructure Between AI Agents and the EVM

https://blog.bridgexapi.io/the-missing-infrastructure-between-ai-agents-and-the-evm
1•Bridgexapi•45m ago•0 comments

Fable: Two edges of one opinion, on a model switched off

https://rebraining.org/fable
1•Jakko-KAAMOS•47m ago•0 comments

'Tell Him He's a Piece of Shit': Meta's New AI Unit Is a Total Mess

https://www.wired.com/story/mark-zuckerberg-meta-employee-meeting-interrupt-ai/
27•momentmaker•53m ago•14 comments

Let's Destroy American Science

https://nasawatch.com/policy/lets-destroy-american-science/
8•voxadam•56m ago•0 comments

Russian families use AI to 'resurrect' loved ones killed in Ukraine

https://www.bbc.com/news/articles/cwy24v72n19o
3•breve•57m ago•0 comments

Monero Inflation Checker

https://www.moneroinflation.com/
1•Cider9986•1h ago•0 comments

Switzerland to vote on plan to cap population at 10 million

https://www.bbc.com/news/articles/cx23kz7e76po
2•breve•1h ago•0 comments

4 things to know about the new sunscreen ingredient the FDA approved

https://www.npr.org/2026/06/13/nx-s1-5856385/sunscreen-skin-protection-bemotrizinol
33•mikhael•1h ago•2 comments

The "Best" HN Comments

https://news.ycombinator.com/bestcomments
3•embedding-shape•1h ago•0 comments

There is no such thing as an AI 'artist'

https://www.spiked-online.com/2026/06/07/there-is-no-such-thing-as-an-ai-artist/
4•mikelgan•1h ago•2 comments

The AI supply chain is a software supply chain with new failure modes

https://blog.r-lopes.com/newsletter/2026-06-03
3•dovelome•1h ago•0 comments

Fable 5: They switched off my AI mid-build. The timeline is the story

https://medium.com/@alirezarezvani/fable-5-anthropic-and-us-gorvernment-how-ai-export-controls-ju...
2•jungard•1h ago•0 comments

FDA OKs first new sunscreen ingredient in more than 25 years

https://apnews.com/article/sunscreen-fda-bemotrizinol-ingredient-uva-protection-9b9c7e04b418b3c9c...
17•marc__1•1h ago•4 comments

The Future of Software Engineering Is Here; It's Just Not Evenly Distributed

https://twitter.com/jmugan/status/2065962078322438524
2•jmugan•1h ago•0 comments

Goldman and Morgan Stanley to Pocket $100M Each in SpaceX IPO Fees

https://www.wsj.com/livecoverage/spacex-ipo-stock-market-06-12-2026/card/goldman-and-morgan-stanl...
4•vismit2000•1h ago•0 comments
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.