frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Silicon Valley Splits over Closing the Borders to Chinese A.I

https://www.nytimes.com/2026/07/25/technology/open-source-silicon-valley-china.html
1•thm•3m ago•0 comments

NASA Fire Information Interactive Map

https://firms.modaps.eosdis.nasa.gov/map/#d:2026-07-20..2026-07-26;@19.0,1.5,3.0z
1•Eridanus2•5m ago•0 comments

Ask HN: Graal VM Relevance

1•sid_op•6m ago•0 comments

Typhoon Noul forces more than 715,000 from homes and cancels flights

https://www.theguardian.com/world/2026/jul/26/typhoon-noul-china-hong-kong
1•tosh•6m ago•0 comments

The Assault on Science Funding Continues

https://www.science.org/content/blog-post/assault-science-funding-continues
1•mooreds•7m ago•0 comments

What a $15 pint of ice cream says about the economy

https://www.cnn.com/2026/07/25/economy/15-usd-pint-ice-cream-economy
1•mooreds•7m ago•0 comments

The New AI Superpowers: Focus and Followthrough

https://www.rickmanelius.com/p/the-new-ai-superpowers-focus-and
1•mooreds•8m ago•0 comments

Romanian shoots down drone entering country's airspace for third day in a row

https://www.france24.com/en/europe/20260726-romanian-jet-shoots-down-drone-entering-country-airsp...
1•olexsmir•14m ago•0 comments

Meta faces higher borrowing costs in latest $12B data centre financing

https://www.ft.com/content/822628c5-4f9c-47db-bd27-f3ad7f841700
2•1vuio0pswjnm7•16m ago•0 comments

Managing File Descriptors for Durability and Performance

https://blog.atimin.dev/handling-file-descriptors/
1•flipback•16m ago•0 comments

Building Drizzle ORM

https://underdogfounders.substack.com/p/the-story-of-building-drizzle-orm
1•matijash•17m ago•0 comments

LoRA Fine-Tuning and Profiling of a 0.5B Language Model on Apple Silicon

https://zenodo.org/records/21541601
1•tanmaydesh5189•18m ago•0 comments

Show HN: External KV Cache Offloading Cuts Long Horizon Inference Costs by 50%

https://github.com/openlake-project/openlake
12•arnav__1•18m ago•0 comments

Show HN: Temporal Context Map

https://ab.neudice.eu/
2•zebike•21m ago•0 comments

The Money AMD Is Chasing with Its Rackscale AI System Roadmaps

https://www.nextplatform.com/compute/2026/07/24/the-money-amd-is-chasing-with-its-rackscale-ai-sy...
1•rbanffy•24m ago•0 comments

Introduction to Microsoft Excel 1990 with Jan Brehm

https://www.youtube.com/watch?v=kOO31qFmi9A
2•chistev•24m ago•0 comments

Shared Claude chats showing up in Google results

https://old.reddit.com/r/ClaudeAI/comments/1v6fiyj/you_can_view_a_lot_of_shared_conversations_via/
1•dgellow•26m ago•0 comments

US tech groups cut 140k jobs despite AI spending boom

https://www.ft.com/content/96a33881-27fd-42cf-8cff-4cbc87fc835f
1•1vuio0pswjnm7•27m ago•0 comments

Modern and Minimal Linux: NixOS and Noctalia and Labwc Flake

https://github.com/grigio/nixos-noctalia-labwc-flake
3•grigio•28m ago•0 comments

Goodbye Microslop: Finally Moved to Codeberg

https://nezutero.dev/goodbye-microslop-finally-moved-to-codeberg/
1•nezutero•28m ago•0 comments

Kahneman's Cabs: Solving Probability Puzzles

https://www.neelocean.com/kahnemans-cabs/
1•thinkingemote•29m ago•0 comments

Show HN: Reverse Minesweeper

https://sunflowersgame.com/
3•pompomsheep•30m ago•2 comments

Job Search, in One Intelligent Workspace

https://www.karyfy.com
1•negiadventures•31m ago•0 comments

Show HN: Virtual time engine to record HTML to 60fps MP4, no drops

https://zlvox.com/tools/html-to-video
1•mrdisloyal•33m ago•0 comments

An update on beta-alanine supplementation for athletes (2020)

https://www.gssiweb.org/sports-science-exchange/article/an-update-on-beta-alanine-supplementation...
1•Jazgot•34m ago•0 comments

CVE-2026-49176 Exploit Development: WalletService to System

https://davidcarliez.github.io/blog/cve-2026-49176-walletservice-to-system/
1•haeseong•35m ago•0 comments

Google's AI Spending Spree Has Investors Nervous

https://www.wsj.com/tech/ai/alphabet-googl-q2-earnings-report-2026-stock-f6bdd223
1•1vuio0pswjnm7•36m ago•0 comments

Google Discloses $94.1B in SpaceX Stock, Marking 6% Stake

https://www.wsj.com/tech/google-discloses-94-1-billion-in-spacex-stock-marking-6-stake-91655d7c
24•1vuio0pswjnm7•37m ago•11 comments

Islamist terrorist attack in Berlin Pride event

https://www.dw.com/en/germany-classifies-berlin-pride-ramming-as-terror-attack/live-78117180
2•sajithdilshan•41m ago•0 comments

Show HN: I got 32-bit Bun running on Windows

https://twitter.com/_vkaku/status/2081356483040620981
1•vkaku•41m ago•1 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.