frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Flinku – I built a Firebase Dynamic Links replacement after the shutdown

https://www.flinku.dev/
1•luky_dev•1m ago•0 comments

IBM folds to Trump anti-DEI push, admits no misconduct but pays $17M penalty

https://arstechnica.com/tech-policy/2026/04/ibm-folds-to-trump-anti-dei-push-admits-no-misconduct...
2•Growtika•4m ago•0 comments

The "Bug" Heard 'Round the World [pdf]

https://www5.in.tum.de/~huckle/space_.pdf
1•danielovichdk•5m ago•0 comments

Roblox devs now need a subscription to share their games freely

https://devforum.roblox.com/t/new-publishing-requirements-evaluation-process-for-games/4573166
2•hallole•10m ago•0 comments

Show HN: SCP – A protocol that drops LLM API calls to zero in 60fps physics loop

https://github.com/srk0102/plexa
1•srk0102•11m ago•0 comments

Generative AI in Banking: Top Use Cases and Benefits

https://www.kellton.com/kellton-tech-blog/generative-ai-in-banking
1•johnjosephkt•13m ago•0 comments

Ask HN: LeetCode, anyone still doing it?

1•kwar13•15m ago•0 comments

DeepDive – Autonomous OSINT investigation tool with 3D graph

https://github.com/Sinndarkblade/deepdive
1•sinndarkblade•25m ago•1 comments

MOS tech 6502 8-bit microprocessor in pure SQL powered by Postgres

https://github.com/lasect/pg_6502
1•adunk•27m ago•0 comments

Microsoft exec suggests AI agents will need to buy licenses, just like employees

https://www.businessinsider.com/microsoft-executive-suggests-ai-agents-buy-software-licenses-seat...
1•maxloh•28m ago•0 comments

What Comes After Vibe Coding

https://blog.bijup.com/what-comes-after-vibe-coding
2•andreirx•32m ago•1 comments

Show HN: One-command deploys from your terminal with CreateOS CLI

https://nodeops.network/createos/docs/CLI/Overview
1•alex_creates•32m ago•0 comments

Pruner: Give AI coding agents the right context in one shot

https://github.com/heikki-laitala/pruner
2•xfiler•34m ago•0 comments

Dependency cooldowns turn you into a free-rider

https://calpaterson.com/deps.html
1•calpaterson•40m ago•0 comments

Bypass Paywalls Clean Chrome

https://gitflic.ru/project/magnolia1234/bypass-paywalls-chrome-clean
2•Cider9986•40m ago•2 comments

Multi-Agentic Software Development Is a Distributed Systems Problem

https://kirancodes.me/posts/log-distributed-llms.html
2•tie-in•41m ago•0 comments

Sam Altman: Man charged with attempting to murder OpenAI boss

https://news.sky.com/story/sam-altman-man-charged-with-attempting-to-murder-openai-boss-13531548
2•taspeotis•44m ago•0 comments

UpDown: Efficient Manycore based on Many Threading & Scalable Memory Parallelism

https://people.cs.uchicago.edu/~aachien/lssg/research/10x10/ics26-single-chip-updown.pdf
4•matt_d•45m ago•0 comments

TanStack Start Now Support React Server Components

https://tanstack.com/blog/react-server-components
17•polywock•45m ago•8 comments

How the corpse flower came to be so weird

https://www.scientificamerican.com/article/how-the-corpse-flower-evolved-its-bizarre-traits/
1•1659447091•48m ago•0 comments

HyperVenom: Using Hyper-V for Ring -1 Control from Usermode

https://gsmll.github.io/hypervenom/writeup/
2•claykettle•50m ago•0 comments

Modern Git based version control with parallel and stacked branches

https://gitbutler.com/
1•rushil_b_patel•52m ago•0 comments

Can Germany restart its nuclear power program?

https://www.politico.eu/article/germany-berlin-nuclear-is-over-the-debate-isnt/
1•leonidasrup•53m ago•0 comments

Introduction to Spherical Harmonics for Graphics Programmers

https://gpfault.net/posts/sph.html
2•nicebyte•58m ago•0 comments

Hackers Reveal Rockstar Earns over $1M a Day from GTA Online

https://kotaku.com/hackers-reveal-rockstar-earns-over-1-million-a-day-from-gta-online-2000687207
1•jmsflknr•1h ago•0 comments

Show HN: Groupr – Rust CLI that sorts files into subfolders by extension

https://github.com/TimFinnigan/groupr
1•timfinnigan•1h ago•0 comments

Show HN: Shloka Artha [Word-by-Word Meanings for Shlokas]

https://shlokartha.in/
1•init0•1h ago•0 comments

Show HN: Deflect One – command line dashboard for managing Linux servers via SSH

https://github.com/Frytskyy/deflect-one
2•whitemanv•1h ago•1 comments

Show HN: 2nnel – self-hosted ngrok with one-click framework-agnostic deployment

https://github.com/22or/2nnel
1•rogerdodgerwang•1h ago•0 comments

Need feedback on sandflare.io – AI Agent Sandboxes with

2•ajaysheoran2323•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•10mo 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•10mo 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•10mo 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•10mo 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.