frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Working on a crypto market and portfolio visualization tool – feedback welcome

https://blockviz.xyz
1•blockviz•1m ago•1 comments

Ask HN: Any experience with high risk payment processors

2•ClipNoteBook•2m ago•0 comments

enclose.horse

https://enclose.horse
1•neighborly•4m ago•0 comments

Echoes from the Moon

https://arxiv.org/abs/0903.3367
1•ColinWright•4m ago•0 comments

The Last of Us – Fighting the EU Surveillance Law Apocalypse [video]

https://media.ccc.de/v/39c3-the-last-of-us-fighting-the-eu-surveillance-law-apocalypse
2•nickslaughter02•6m ago•0 comments

Ask HN: Alternatives to .com: Xxxlabs.com vs. XXX.software

1•finnvyrn•7m ago•1 comments

LT→A: Import your highlights from LiquidText to Are.na

https://gregwolanski.com/lt2a/
1•gregwolanski•8m ago•0 comments

16-bit Intel 8088 chip by Charles Bukowski

https://mypoeticside.com/show-classic-poem-4359
1•sovietswag•11m ago•0 comments

Election betting on prediction markets apps is set to boom ahead of midterms

https://www.npr.org/2025/12/23/nx-s1-5647749/rise-of-prediction-markets
2•mhb•15m ago•0 comments

Show HN: Productivity app that blocks you at 10:1 work-to-rest ratio

https://app.kensho.zone
1•kenshozone•15m ago•0 comments

Tesla Model 3 sedans face federal safety probe over hidden emergency releases

https://www.latimes.com/business/story/2025-12-26/tesla-model-3-sedans-face-federal-safety-probe-...
5•1vuio0pswjnm7•16m ago•0 comments

1Password extension is injecting Prism.js and breaking all <code> highlighting

https://twitter.com/youyuxi/status/2005904473332564339
6•HatchedLake721•17m ago•0 comments

Busy Work

https://en.wikipedia.org/wiki/Busy_work
2•Hbruz0•18m ago•0 comments

How to send data from a Python server to C++ program

1•ThEoDorr•19m ago•0 comments

When the line stops going up

https://www.coryzue.com/writing/the-line/
2•czue•19m ago•0 comments

A 3D multiplayer driving/exploration game on Mapbox

https://github.com/WilliamAvHolmberg/glenn-explore
1•mercenario•20m ago•0 comments

Americans Hate AI. Which Party Will Benefit

https://www.politico.com/news/magazine/2025/12/28/ai-job-losses-populism-democrats-bernie-sanders...
4•Webstir•21m ago•1 comments

Are these AI prompts damaging your thinking skills?

https://www.bbc.com/news/articles/cd6xz12j6pzo
1•1vuio0pswjnm7•22m ago•0 comments

Decoding a V16 Beacon

https://destevez.net/2025/12/decoding-a-v16-beacon/
3•bearbin•26m ago•0 comments

Show HN: Refactor Vue/React Components with Label Propagation and Claude Code

https://vue-hook-optimizer.vercel.app/
1•huali•26m ago•1 comments

Building a React App with Formally Verified State

https://midspiral.com/blog/building-a-react-app-with-formally-verified-state/
2•namin•26m ago•1 comments

Show HN: Collaborative code playground in a single <1MB HTML file

https://github.com/micouy/koper
1•micouay•28m ago•0 comments

Show HN: Paper Tray – dramatically better file organization for Google Drive

https://www.papertray.ai/
1•affine_variety•29m ago•0 comments

Free macOS app to manage SQL databases without writing SQL

https://vps-commander.com/data-builder-macos-free-version/
1•tkrenn06•32m ago•0 comments

Show HN: Terminalot – A local-first, open-core SSH terminal with AI copilot

https://github.com/linkeli-labs/terminalot
1•linkeli•33m ago•0 comments

Why isn't there a ChatGPT for social media

1•NibezaK•35m ago•0 comments

MH370 vanished in 2014.New search aims to find answers families desperately want

https://www.abc.net.au/news/2025-12-30/mh370-search-resumes-for-malaysia-airlines-missing-plane/1...
3•evolve2k•36m ago•0 comments

Ionice(1) – Linux Manual Page

https://man7.org/linux/man-pages/man1/ionice.1.html
2•keepamovin•36m ago•0 comments

Looking at 2026 Through the Eyes of 1926

https://www.nytimes.com/2025/12/08/special-series/century-history-reflection-2026.html
1•cainxinth•37m ago•0 comments

Open Badges

https://openbadges.org/
1•Lwrless•37m ago•0 comments
Open in hackernews

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

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