frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

So This is Peak Smartphone [video]

https://www.youtube.com/watch?v=c347oYQO57A
1•thelastgallon•9m ago•0 comments

The most overenginereed Chromium extension?

https://www.superchargebrowser.com/performance/
1•superchargeext•11m ago•0 comments

Ubuntu 26.04 is more than just a performance bump for thrill-seeking gamers

https://www.zdnet.com/article/ubuntu-26-04-performance/
1•teleforce•12m ago•0 comments

Reverse-engineering infrared-based electronic shelf labels

https://www.furrtek.org/?a=esl
1•pabs3•13m ago•0 comments

Rivian R2 won't have A/C buttons followed by CEO's decision

https://theevreport.com/rivian-r2s-screen-heavy-interior-was-a-top-down-ceo-decision
1•vincentchau•18m ago•0 comments

1981 Spanish cooking oil disaster

https://en.wikipedia.org/wiki/Toxic_oil_syndrome
1•burnt-resistor•18m ago•1 comments

Zero Days Clock

https://zerodayclock.com/
1•baxtr•18m ago•0 comments

Paraloid B-72

https://en.wikipedia.org/wiki/Paraloid_B-72
2•Ariarule•21m ago•0 comments

Five Simple Steps to Fix America

https://geohot.github.io//blog/jekyll/update/2026/04/18/five-simple-steps.html
1•inatreecrown2•24m ago•0 comments

The Dangers of Nicotine Biohacking

https://www.lung.org/blog/nicotine-biohack-dangers
1•KnuthIsGod•24m ago•0 comments

GPT 5.5 Released in Codex

3•zuzululu•25m ago•2 comments

An Algorithmic Reconstruction of Normalisation by Evaluation

https://yangzhixuan.github.io/NbE.html
1•matt_d•27m ago•0 comments

Global energy markets are on the verge of a disaster

https://www.economist.com/finance-and-economics/2026/04/21/global-energy-markets-are-on-the-verge...
3•petethomas•38m ago•0 comments

Moving a tenant across PostgreSQL instances

https://ananthakumaran.in/2026/04/22/moving-tenant-across-postgresql-instances.html
1•ananthakumaran•41m ago•0 comments

Can EVs kill off petrol cars in China?

https://www.ft.com/content/c78e0368-cc57-4f92-ad62-a073e01ba73d
1•petethomas•44m ago•0 comments

Code, your choice: Netlify's stance on AI training data

https://www.netlify.com/blog/stance-on-ai-training-data/
1•kristianp•46m ago•1 comments

Changes to GitHub Copilot Individual Plans

https://simonwillison.net/2026/Apr/22/changes-to-github-copilot/
2•omer_k•48m ago•0 comments

Bob Dylan – Murder Most Foul (Official Audio) [video]

https://www.youtube.com/watch?v=3NbQkyvbw18
1•hkhn•50m ago•0 comments

The Mattering Instinct: How Our Deepest Longing Drives Us and Divides Us

https://rebeccagoldstein.com/the-mattering-instinct/
1•hkhn•51m ago•0 comments

OpenBSD – LibreSSL 4.3.1 Released

https://www.undeadly.org/cgi?action=article;sid=20260420085845
2•peter_hansteen•52m ago•0 comments

Elon Musk's SpaceX Endgame

https://www.theatlantic.com/technology/2026/04/elon-musk-starlink-satellites/686877/
3•paulpauper•53m ago•0 comments

The State of the Human Rights: April 2026

https://www.amnesty.org/en/documents/pol10/0320/2026/en/
1•hkhn•55m ago•0 comments

Hundreds trying to storm Wisconsin beagle research facility

https://www.msn.com/en-us/news/world/hundreds-trying-to-storm-wisconsin-beagle-research-facility-...
2•rguiscard•55m ago•0 comments

Happiness Feels

https://passiveaggressionoftheworlds.substack.com/p/how-happiness-feels
1•bunson_burner•59m ago•0 comments

Microsoft's GitHub grounds Copilot account sign-ups amid capacity crunch

https://www.theregister.com/2026/04/20/microsofts_github_grounds_copilot_account/
2•gpi•1h ago•0 comments

Ask HN: What Would Make Stack Overflow Great Again?

3•nnurmanov•1h ago•1 comments

Claude 4.7 blocks cyber prompts: before the fact vs. after the fact

https://raxitlabs.com/blogs/claude-47-five-layers-cyber-blocking
2•agairola•1h ago•0 comments

Show HN: XTTV, the App to watch long video from Twitter/X on Apple TV

https://apps.apple.com/us/app/xttv/id6757870255
1•ShawFei•1h ago•0 comments

Cognition without brains? Learning and memory in microorganisms

https://www.sciencedirect.com/science/article/pii/S0966842X26000909
1•the-mitr•1h ago•0 comments

Agent Harness Engineering

https://addyosmani.com/blog/agent-harness-engineering/
3•tanelpoder•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•11mo 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•11mo 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•11mo 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•11mo 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.