frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Lotr

1•coolrad•12m ago•2 comments

Our AI Agents Should Pay the People Who Help Them

https://danielmiessler.com/blog/agents-should-pay-creators
3•walterbell•13m ago•0 comments

Decision 2.0: our newest decision models

https://twitter.com/vllm_project/status/2106193438098256191
2•thedima•15m ago•0 comments

Exam of the Month: All Souls Prize Fellowship Exam

https://alexanderhthompson.substack.com/p/exam-of-the-month-all-souls-prize
1•nicksont•15m ago•0 comments

Agentic Compliance in Finance

https://blog.gigacore.in/series/ai-in-finance/agentic-compliance-an-engineering-approach/
3•Gigacore•18m ago•0 comments

Harness Engineering: Anatomy, Architecture, and Evolution of Coding Agents

https://arxiv.org/abs/2609.00006
2•Anon84•20m ago•1 comments

Cure for Cancer (Pure Math Theorem) [pdf]

https://github.com/LeBaux/lebaux.github.io/blob/main/cancer-cure-draft.pdf
1•lebaux•22m ago•2 comments

MacTrove – Classic Macintosh Software Archive

https://mactrove.com/
2•andsoitis•22m ago•0 comments

European Commission Staff Dislike Their 'Sovereign' Alternative to Teams

https://gizmodo.com/european-commission-staff-really-dislike-their-sovereign-alternative-to-micro...
1•HiroProtagonist•24m ago•0 comments

Researcher at Russian plague laboratory dies of 'unknown' infection

https://www.cnn.com/2026/10/04/europe/russia-laboratory-plague-accident-intl
4•wslh•25m ago•1 comments

MacSurf – classic Mac browser that loads today's web

https://macsurf.org/
2•michaelsbradley•26m ago•0 comments

Self-hosted HTTP tunnels with SSH and Nginx

https://vincent.bernat.ch/en/blog/2026-http-over-ssh
2•renehsz•26m ago•0 comments

The Power of Coincidence

https://www.theatlantic.com/newsletters/2026/10/strange-power-of-coincidence/688880/
2•andsoitis•27m ago•0 comments

Show HN: xxWikiJS knowledge base from your docs, answers with verified citations

https://gmaterni.github.io/wikijs/wikijs.html
2•gmaterni•29m ago•0 comments

What If My Theory of Everything Is Wrong?

https://peterbriaros.substack.com/p/what-if-my-theory-of-everything-is
2•tgraf_80•31m ago•0 comments

Show HN: I built an square foot measuring app

https://play.google.com/store/apps/details?id=com.sqftcalc.app&hl=en_US
1•Gigacore•34m ago•0 comments

Erm, does anyone still bother hiring in US/UK?

https://www.hotsourced.io/talent-marketplace
6•andrewbrowning•34m ago•5 comments

Show HN: Sortbot.io – Your physical inventory, with an API and MCP access

https://www.sortbot.io
1•obilgic•40m ago•0 comments

Muse AI on Xteink X3 E-reader

https://charoori.com/blog/muse-on-xteink-x3/
1•Exorust•41m ago•0 comments

Generalization Dynamics of LM Pre-Training

https://www.alphaxiv.org/abs/2609.33150
1•gmays•42m ago•0 comments

San Francisco's car crime has plunged. How much credit does Flock deserve?

https://www.npr.org/sections/planet-money/2026/10/02/g-s1-146060/san-franciscos-car-crime-has-plu...
3•pseudolus•42m ago•1 comments

The Lenovo Chromebook Plus

https://taoofmac.com/space/reviews/2026/10/04/1800
1•rcarmo•43m ago•0 comments

Ask HN: Mainstream media overplaying the threat of AI, or industry underplaying?

1•AbstractH24•45m ago•0 comments

AI Backers Sound the Alarm About Safety

https://www.bloomberg.com/news/newsletters/2026-10-04/ai-backers-sound-the-alarm-about-safety
1•ent101•46m ago•0 comments

AI doesn't need 'superintelligence' or evil intent to start a nuclear war

https://thebulletin.org/2026/10/ai-doesnt-need-superintelligence-or-evil-intent-to-start-a-nuclea...
5•bookofjoe•48m ago•0 comments

Show HN: Every click on this page draws a new Maurer rose

https://counter.maricakes.de/
1•jantuss•50m ago•0 comments

How Kyiv cracked Russia’s kill zone and got its tanks back in the fight

https://www.telegraph.co.uk/world-news/2026/10/03/how-ukraine-cracked-russias-kill-zone/
2•cisc•51m ago•0 comments

Show HN: NESH – A from-scratch UEFI shell with BASIC scripting

https://nesh.nicfio.it/
1•nicfio•58m ago•0 comments

Proposed Solution to Global Warming (2006)

https://qntm.org/global
2•andsoitis•1h ago•1 comments

Typst 0.15 Contains Multitudes

https://typst.app/blog/2026/typst-0.15/
6•birdculture•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.