frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kicking the Tires on Jev with 2048

https://gist.github.com/cablehead/bdf9ad946ceb26d9008976e49c9bfbbb
1•0l•53s ago•0 comments

Is Jev the general-purpose classifier we've been waiting for?

https://twitter.com/kris_cvetko/status/2101614168763695308
1•kncvetko•2m ago•1 comments

Dragonfly 2.0: more performance for Redis and Memcached replacement

https://www.phoronix.com/news/Dragonfly-2.0-Released
2•joshcsimmons•3m ago•0 comments

AI and the Destruction of the Creative Commons

https://www.chesterwisniewski.com/post/2026-09-13-ai-is-destroying-the-creative-commons/
1•rakel_rakel•4m ago•0 comments

Show HN: WTF > Auto-check what your coding agent changed

https://github.com/LinusInnovator/wtf
1•Linusinnovator•6m ago•0 comments

Joe Shipman proves marked ruler and compass solves the general quintic

2•jjgreen•15m ago•0 comments

PDF Forgeries Are Surprisingly Rare (2022)

https://gwern.net/blog/2022/pdf-forgery
2•1317•15m ago•0 comments

Hyperbolic Navigation

https://en.wikipedia.org/wiki/Hyperbolic_navigation
1•Eridanus2•19m ago•0 comments

Away Goals Rule

https://en.wikipedia.org/wiki/Away_goals_rule
1•chistev•19m ago•0 comments

Enterprise Cyber Risk Management

https://andersenlab.com/services/cybersecurity-risk-management
1•andersen_lab•25m ago•0 comments

Be Careful with Your Select * Queries

https://notesonsystems.com/articles/why-im-done-with-select-star
1•theanonymousone•30m ago•1 comments

TeaonherChecker

https://teaonher.org
1•thefirstname322•31m ago•0 comments

Leaping Sun Dogs (2016) [video]

https://www.youtube.com/watch?v=KPPaGmtuHCY
1•joebig•34m ago•0 comments

Jev is the fastest-adopted model in AI Gateway history

https://vercel.com/blog/ai-gateway-jev-model-launch
1•flashbrew•34m ago•1 comments

A font that reads what you wrote

https://rohanadwankar.github.io/posts/semfont.html
1•RohanAdwankar•34m ago•1 comments

A deep dive into Jev, TypeSafe's System One model

https://flaviocopes.com/jev/
1•sts153•35m ago•0 comments

CoyoPedal – Full-Size Neural Amp Modeler Captures on an ESP32-S3

https://github.com/dashersw/coyopedal
1•arbayi•35m ago•0 comments

I'm so bad at billiards that I ended up in the hyperbolic plane [video]

https://www.youtube.com/watch?v=kL9BTbIGxLg
1•vismit2000•35m ago•0 comments

MIT Just Proved LLMs Will Stop Getting Smarter, and Money Won't Fix It [video]

https://www.youtube.com/watch?v=6xQ8LQfkBg4
1•bArray•39m ago•0 comments

Show HN: Delightful Cells – reliable AI batch processing for spreadsheets

https://delightfulcells.com
1•sumtsui•41m ago•1 comments

Clawptcha: Reverse Captcha

https://clawptcha.com/
1•Kotlopou•46m ago•0 comments

Neutron Radiation, Emission and Scattering (Neutron Chemistry)

https://www.ossila.com/pages/neutron-radiation
1•peter_d_sherman•46m ago•0 comments

Drop-in Django app to serve a decent LLM-ready documentation site

https://mdjango.chesselink.com/
3•fluxmatix•54m ago•1 comments

I built an extension that hides your personal information from AI

https://github.com/arikchakma/opencloak
2•arikchakma•57m ago•0 comments

Show HN: I-server: Hide server using ICMP reflection/Destination Unreachable

https://github.com/hajoon22/i-server
2•hajoon22•1h ago•0 comments

Benchmarking Wild vs. Mold

https://davidlattimore.github.io/posts/2026/09/18/benchmarking-wild-vs-mold.html
6•birdculture•1h ago•0 comments

Microsoft agentically ports Copilot runtime to Rust for $120K

https://www.theregister.com/devops/2026/09/18/microsoft-agentically-ports-copilot-runtime-to-rust...
5•pjmlp•1h ago•0 comments

Why China is pushing back on US warnings over rapid AI development

https://www.theguardian.com/world/2026/sep/20/why-china-is-pushing-back-on-us-warnings-over-rapid...
5•chrisjj•1h ago•0 comments

Boston to Calcutta Ice Trade Began with One Shipment

https://curiowire.com/article/556
3•thunderbong•1h ago•0 comments

Show HN: Book recommendations with live library availability

https://leafle.nanosheep.net
3•kidnoodle•1h ago•4 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.