frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

It's 21 days until the US midterms: This is How We Win

https://www.theguardian.com/commentisfree/2026/oct/09/its-21-days-until-the-us-midterms-this-is-h...
1•hkhn•1m ago•0 comments

How to Radicalize Your Friends into NixOS

https://squirrel.talosvault.net/blog/nix-radicalize/
1•SquirrelModeler•5m ago•0 comments

US hits Bank of America with $1.2B fine

https://apnews.com/article/treasury-bank-of-america-money-laundering-29013b2c8f08a3a8d579a96721ed...
5•geox•10m ago•1 comments

How well does AI predict humans?

https://simulacrabench.org/
1•indra0s•11m ago•0 comments

Advanced Window Trading Terminal

https://abelhelton.gumroad.com/l/vantex-desktop
1•jspfbsj•23m ago•0 comments

Build Independently. Win Together: Why I Built IndieCrew

https://indiecrew.win/news/build-independently-win-together-why-i-built-indiecrew-1a37daa5
2•zd_coinrule•24m ago•0 comments

Ukraine Just Opened a New Front – By Roman Sheremeta

https://economicsofpower.substack.com/p/ukraine-just-opened-a-new-front
4•rbanffy•27m ago•0 comments

FastH3-Omni: The best open-source H3 model

https://www.reactor.inc/models/fast-h3-omni
1•ahmedahres•28m ago•0 comments

Get an oncologist's perspective on your cancer care

https://intake.sagelyhealth.com
1•peerless-app•28m ago•0 comments

Show HN: Jevcrawl – A web crawler for AI agents with no LLM in the crawl loop

https://github.com/RayenMlayeh/jevcrawl
2•rayenmlayeh•31m ago•0 comments

Chris Wickham RIP

https://www.markkoyama.com/p/chris-wickam-rip
2•paulpauper•33m ago•1 comments

Swarm Intelligence

https://kevinkelly.substack.com/p/swarm-intelligence
4•paulpauper•33m ago•0 comments

Berry, Bresnahan, and Pakes (Maybe) Win the Nobel Prize

https://nicholasdecker.substack.com/p/berry-bresnahan-and-pakes-maybe-win
1•paulpauper•34m ago•0 comments

Did Ukraine's drone strikes on Yandex data centers silence Russian bots?

https://mashable.com/tech/ukraine-strikes-yandex-data-center-bot-traffic-decline
2•ryan_j_naughton•37m ago•0 comments

AI's quiet safety gatekeepers are stepping into the spotlight

https://www.cnbc.com/2026/10/11/ais-quiet-safety-gatekeepers-are-stepping-into-the-spotlight.html
1•gmays•37m ago•0 comments

Sexually Transmitted Diarrhea Is Exploding, and Growing Resistant to Medicine

https://www.sciencealert.com/sexually-transmitted-diarrhea-is-exploding-in-the-us-and-its-growing...
2•Teever•38m ago•0 comments

Show HN: 3D Studio in the Browser

https://3d.puter.com/
2•ent101•42m ago•0 comments

Amex introduces a framework to prevent AI agents from unauthorized purchases

https://techcrunch.com/2026/10/13/amex-introduces-a-framework-to-prevent-ai-agents-from-making-un...
2•6thbit•42m ago•0 comments

The Links Between Cannabis and Crime

https://www.rand.org/pubs/external_publications/EP71427.html
2•coloneltcb•45m ago•0 comments

Could I make six figures from my couch? Influencers said yes – so I tried

https://www.theguardian.com/business/ng-interactive/2026/oct/13/influencers-passive-income-side-h...
2•teleforce•46m ago•2 comments

Show HN: Pulse Local, a Mac budgeting app whose AI models run on your machine

https://pulseos.finance
12•niztk•52m ago•2 comments

Windows native trading app Full Ownership

https://abelhelton.gumroad.com/l/vantex-trading
2•jsjcisjcj•55m ago•1 comments

Show HN: Wonderhop – A daily game: guess what most people say, or what none do

https://wonderhop.io/en/
2•mtlduo•56m ago•1 comments

Sonic CD / FTL and Hotline Miami on the Web

https://remake.games/
1•nihey•57m ago•2 comments

Botflix TV – 24/7 Robot TV. For robots

https://botflix.tv/
1•cheschire•1h ago•2 comments

Warning: Relying on a 'phone can lead to disaster [video]

https://www.youtube.com/watch?v=b9YASgAeCoM
2•GarnetFloride•1h ago•1 comments

Biscoff Cookies Were Supposed to Be Temporary. Then Passengers Fell in Love

https://www.seriouseats.com/biscoff-history-12168161
1•mhb•1h ago•0 comments

What is SpacetimeDB? SpacetimeDB is a relational database that is also a server

https://github.com/ClockworkLabs/SpacetimeDB
1•Bluestein•1h ago•0 comments

Domain Health

3•anjalibery•1h ago•0 comments

Lotus Improv on the NeXT

https://stonetools.ghost.io/lotusimprov-next/
1•ohjeez•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.