frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Throughput Upgrade (With Train Illustrations) Blog

https://blog.healthchecks.io/2025/07/throughput-upgrade-with-train-illustrations/
1•tosh•3m ago•0 comments

GeoGPT – Chat-controlled GIS app built from a Jupyter Notebook

https://mljar.com/blog/chatgpt-gis-app-jupyter-notebook/
1•pplonski86•3m ago•0 comments

Superposition Yields Robust Neural Scaling

https://arxiv.org/abs/2505.10465
1•kioku•7m ago•0 comments

Canada Warms Up to EVs from China

https://www.caranddriver.com/news/a70188525/chinese-evs-north-america/
1•breve•8m ago•0 comments

Khosrow Alikordi: Lawyer for Mahsa Amini

https://en.wikipedia.org/wiki/Khosrow_Alikordi
1•ukblewis•9m ago•0 comments

Free async standup bot for Slack – looking for feedback

https://www.vereda.ai/free-slack-standup-bot
1•awightman•10m ago•1 comments

AI Incident Roundup – November and December 2025 and January 2026

https://incidentdatabase.ai/blog/incident-report-2025-november-december-2026-january/
1•YeGoblynQueenne•14m ago•0 comments

TikTok hit with charges by EU for its addictive features

https://www.reuters.com/business/media-telecom/tiktok-hit-with-charges-breaching-eu-online-conten...
3•hackerbeat•17m ago•0 comments

Signy: Signed URLs for Small Devices

https://github.com/golioth/signy
1•hasheddan•18m ago•0 comments

Shadcn/Create in Figma

https://www.shadcndesign.com/blog/shadcn-create-in-figma
1•figmaster•19m ago•0 comments

Show HN: Langraph Networks as Equations

https://github.com/kummahiih/python-langgraph-equations
1•kummap•19m ago•0 comments

Bui – TUI for painless Bubblewrap sandboxing

https://smaller.fish/posts/bubblewrap_tui
1•smallerfish•19m ago•0 comments

John Haugeland on the failure of micro-worlds

https://blog.plover.com/tech/gpt/micro-worlds.html
1•robinhouston•23m ago•0 comments

EC preliminarily finds TikTok's addictive design is Digital Services Act breach

https://ec.europa.eu/commission/presscorner/home/en
2•u1hcw9nx•25m ago•1 comments

Ask HN: XCancel but for Instagram?

2•Nurbek-F•25m ago•0 comments

Toyota retains top auto crown in 2025 with record sales

https://www.reuters.com/business/autos-transportation/toyota-retains-top-auto-crown-2025-with-rec...
2•breve•28m ago•0 comments

Iranian regime propaganda floods Wikipedia

https://www.neutralpov.com/p/a-flood-of-iranian-propaganda-on
1•ukblewis•29m ago•0 comments

Show HN: Gazill – Save your code, it's live. Built for vibe coders and agents

1•niklai•29m ago•0 comments

Show HN: Grok Prompts – AI image and video generator with 500 curated prompts

https://grokprompts.app/
1•Yreminder•33m ago•0 comments

Library of Babel 3D

https://library-of-babel-3d.netlify.app/
1•m-hodges•35m ago•0 comments

Amara

https://amara.01c.ai/
2•ashkan01c•35m ago•2 comments

A curated list of best Python books

https://github.com/lara-west/PythonBooks
1•mahsima•37m ago•0 comments

Monty – A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
2•areski•37m ago•0 comments

A startup copied my landing page (and then gave me great feedback on it)

https://blog.dahl.dev/posts/startup-copied-my-design/
2•aleda145•40m ago•0 comments

US Immigration on the Easiest Setting

https://pluralistic.net/2026/02/06/doge-ball/#n-600
9•headalgorithm•40m ago•1 comments

Trois-Rivières, le jeu vidéO

https://www.trois-rivieres.net/
2•JeanKage•40m ago•0 comments

Show HN: PromptHub – 2000 Free AI Prompts for ChatGPT and Midjourney

https://promptshub.shop
1•meimeixoxi•41m ago•0 comments

First Proof: Research-Level Math for AI Evaluation

https://1stproof.org
1•panic•43m ago•0 comments

Show HN: An app to use Instagram without Reels on iOS

https://apps.apple.com/us/app/timecap-limit-screen-time/id6737515680
1•antoferra•45m ago•0 comments

Need feedback for AI tool that lets non-technical users query Postgres

2•dimitsapis•52m ago•0 comments
Open in hackernews

Show HN: Brainfuck to RISC-V JIT compiler written in Zig

https://github.com/evelance/brainiac
5•0x000xca0xfe•8mo 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•8mo 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•8mo 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•8mo 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.