frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

"we are not yet seeing spillovers from tariffs, [and] energy price shocks"

https://www.federalreserve.gov/newsevents/speech/jefferson20261001a.htm
1•Den_VR•1m ago•1 comments

Larceny – a Claude Code plugin that runs a team of agents on GitHub

https://github.com/nestedmind/larceny
1•nestedmind•1m ago•0 comments

zkAPI: private usage credits for any API

https://blog.ethereum.org/2026/10/01/introducing-zkapi
1•jtraglia•2m ago•0 comments

TurboNotes: Local-first Markdown notes, Turbo Pascal like looks, saves to GitHub

https://turbonotes.net/
1•vadepaysa•4m ago•0 comments

With most information hidden, the game Stratego had stumped AI–until now

https://arstechnica.com/science/2026/10/ai-finally-beat-the-best-stratego-player-in-history-and-d...
1•samizdis•4m ago•0 comments

Show HN: Janus – Go binary that runs GGUF models via Vulkan on AMD/Intel/Nvidia

https://github.com/Vibra-Ingenn/Janus
1•Maverick617•5m ago•0 comments

ESP-SDR uses undocumented raw IQ capture of ESP32 to make software defined radio

https://blog.adafruit.com/2026/09/30/esp-sdr-uses-undocumented-raw-i-q-capture-of-esp32-to-make-s...
1•zoobab•5m ago•0 comments

AI is not "just a tool"

https://brettcodes.com/ai-is-not-just-a-tool/
1•Muhammad523•7m ago•0 comments

Show HN: Rhun, an open-source code editor written in assembly

https://rhun.app/
2•vladcodes•9m ago•1 comments

E2E: Next generation E2E testing framework for web and mobile apps

https://github.com/tester-army/e2e
1•handfuloflight•9m ago•0 comments

Griffin: The First Human Interaction Model

https://www.tavus.io/griffin#intro
2•robotswantdata•10m ago•0 comments

Show HN: HeadWater Volume Ingestion Matrix – a production shortcut

https://github.com/PunkiePal/HeadWater-AI-Digital-Products/blob/main/HeadWater_Volume_Ingestion_M...
1•PunkiePal•11m ago•0 comments

Show HN: Premortem – AI agents that red-team your startup idea

https://premortem.site
2•ahoskins•12m ago•0 comments

DeepSeek outage and degraded: API and status page:)

https://status.deepseek.com
1•jmathai•13m ago•0 comments

Nvidia debuted the Open Agent Safety Platform

https://www.nvidia.com/en-us/ai/openshell/
2•aknitb•16m ago•0 comments

19 Out of 21 Late-Model Cars Tested Shared Data with 3rd Parties

https://www.roadandtrack.com/news/a73941763/personal-data-vehicle-security-study/
1•rafaelc•17m ago•0 comments

SvelteKit 3 Release Today

https://next.svelte.dev/docs/kit/migrating-to-sveltekit-3
2•jph•18m ago•1 comments

Manyfold's Agents.md Is Based

https://github.com/manyfold3d/manyfold/blob/main/AGENTS.md
8•adamddev1•18m ago•4 comments

Car Is a Smartphone on Wheels. Here's Who's Listening

https://automatictransmission.khoury.northeastern.edu/index.html
5•rafaelc•18m ago•2 comments

Why doesn't giant AI always overfit?

https://www.echohive.ai/why-giant-ai-doesnt-overfit
1•echohive42•19m ago•0 comments

Now That's an Impurity Story

https://www.science.org/content/blog-post/now-s-impurity-story
1•dcminter•20m ago•0 comments

TCP is failing AI, but Stanford's Homa is here to help

https://www.theregister.com/networks/2026/10/01/tcp-is-failing-ai-but-stanfords-homa-is-here-to-h...
1•joebuckwilliams•22m ago•0 comments

Your folder structure has two jobs, but only does one

https://blog.sterlingfreeman.net/posts/folder-structure-two-jobs/
2•alwaysDrafting•23m ago•0 comments

Cold War spy satellite named after Farrah Fawcett just exploded in space

https://www.popsci.com/science/farrah-fawcett-satellite-explosion-explained/
2•CGMthrowaway•23m ago•1 comments

SvelteKit 3 Is Here

https://svelte.dev/blog/sveltekit-3-is-here
4•sampsn•27m ago•1 comments

ArXiv's Updated Rate Limit Policy

https://blog.arxiv.org/2026/10/01/updated-rate-limit-policy/
2•50kIters•29m ago•0 comments

The failure modes of Claude Code in a guided 60h project

https://hmijail.substack.com/p/building-a-semantic-fuzzer-for-obsidian-sync-in-spite-of-claude-2
1•hmijail•31m ago•1 comments

Antarctica's winter sea ice peaks at 3rd lowest level on record

https://www.nationalheraldindia.com/environment/antarcticas-winter-sea-ice-peaks-at-3rd-lowest-le...
1•wslh•32m ago•0 comments

Show HN: HeadWater B2B Data and AI Kit – A Production Architecture Shortcut

https://github.com/PunkiePal/HeadWater-AI-Digital-Products/blob/main/headwater-b2b-data-purificat...
1•PunkiePal•32m ago•0 comments

cua-speedrun: Standardized Benchmarking of the Speed of Computer-Use Agents

https://cuaspeedrun.com/
1•matt_d•32m 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.