frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ask HN: Others seeing agents do remarkable things when given their own logs?

1•jMyles•4m ago•0 comments

EU investigates Google over 'demoting' commercial content from news media

https://www.theguardian.com/technology/2025/nov/13/eu-investigates-google-search-over-demoting-co...
1•PaulHoule•11m ago•0 comments

Ngrok in your OS X menu bar in 45 lines of code using Swiftbar

https://github.com/PaulMcInnis/ngrok-desktop
1•paulm7242•13m ago•1 comments

Show HN: Net RazorConsole – Build Interactive TUI with Razor and Spectre.Console

https://razorconsole.github.io/RazorConsole/
2•BigBigMiao•16m ago•0 comments

Supreme Court hears case that could trigger big crackdown on Internet piracy

https://arstechnica.com/tech-policy/2025/12/supreme-court-debates-whether-isps-must-kick-pirates-...
1•fizl•16m ago•0 comments

AI hasn't just "learned to lie"

https://iacgm.com/articles/lying/
1•iacgm•19m ago•0 comments

Would love feedback on our new 'Lazy Loading' architecture for PII redaction

https://github.com/rom-mvp/vigil
1•desadas•24m ago•1 comments

Steam on Linux Use Easily Hits an All-Time High in November

https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam
3•systematizeD•28m ago•0 comments

Mathematics Without Numbers (1959)

https://www.jstor.org/stable/20026529?seq=1
1•measurablefunc•29m ago•0 comments

The Waterloo map that Wellington had to know Napoleon would die for

https://ageofrevolution.org/200-object/waterloo-map/
1•gsf_emergency_6•29m ago•0 comments

Prevent a page from scrolling while a dialog is open

https://css-tricks.com/prevent-a-page-from-scrolling-while-a-dialog-is-open/
1•soheilpro•33m ago•0 comments

Claude 4.5 Opus Soul Document, which has now been confirmed by Anthropic

https://gist.github.com/Richard-Weiss/efe157692991535403bd7e7fb20b6695
3•simonw•44m ago•1 comments

MKBHD's wallpaper app Panels is shutting down

https://techcrunch.com/2025/12/01/mkbhds-wallpaper-app-panels-is-shutting-down/
4•coloneltcb•45m ago•1 comments

At the Cottage

https://objects.fun/blog/2025-08-04-cottagecore/
1•adamfuhrer•47m ago•0 comments

Can Messaging Apps Implement SIM Binding Without OS Provider Support?

https://www.medianama.com/2025/12/223-sim-binding-guidelines-os-providers-messaging-apps-impact-u...
1•pabs3•50m ago•0 comments

Why the Sanchar Saathi App Pre-Installation on Smartphones Is a Privacy Concern?

https://www.medianama.com/2025/12/223-govt-sanchar-saathi-app-pre-installation-smartphones-privacy/
1•pabs3•51m ago•0 comments

ProofQR – a blockchain-based QR code verification system

https://www.proofqr.xyz
1•TomatoProgram•52m ago•1 comments

Nimony (eventually Nim 3.0) Design Principles

https://nim-lang.org/araq/nimony.html
2•andsoitis•57m ago•1 comments

Volitional Response Protocol – What happens when LLMs can decline to engage [pdf]

https://github.com/templetwo/Relational-Coherence-Training-RTC/blob/master/RCT_Paper_FINAL.pdf
1•TempleOfTwo•1h ago•2 comments

US air travelers without REAL IDs will be charged a $45 fee

https://apnews.com/article/real-id-fee-airport-security-travel-tsa-fe8c7ed55cf3dacafa10d50cc2112eb7
25•geox•1h ago•19 comments

Around The World, Part 27: Planting trees

https://frozenfractal.com/blog/2025/11/28/around-the-world-27-planting-trees/
6•ibobev•1h ago•0 comments

Wine 10.20

https://gitlab.winehq.org/wine/wine/-/releases/wine-10.20
3•doener•1h ago•0 comments

Lessons from the Frontiers of AI Adoption

https://www.economist.com/business/2025/12/01/lessons-from-the-frontiers-of-ai-adoption
1•andsoitis•1h ago•0 comments

Zig type hackery and memory management

https://joel.id/zig-type-hacker-and-memory-management/
1•andsoitis•1h ago•0 comments

Arcee Trinity Mini: US-Trained Moe Model

https://www.arcee.ai/blog/the-trinity-manifesto?src=hn
9•hurrycane•1h ago•0 comments

Found: The Oldest Sewing Needle

https://www.atlasobscura.com/articles/found-the-worlds-oldest-sewing-needle
1•thunderbong•1h ago•0 comments

GPU deals are drying up fast, but these are the best ones you can still get

https://www.tomshardware.com/pc-components/gpus/gpu-deals-are-drying-up-fast-but-these-are-the-be...
1•doener•1h ago•0 comments

FreeBSD 15.0 is now available

https://lists.freebsd.org/archives/freebsd-announce/2025-December/000213.html
9•cperciva•1h ago•0 comments

Your Phone Isn't a Drug. It's a Portal to the Otherworld.

https://www.nytimes.com/2025/11/28/opinion/internet-phones-social-media-addiction.html
2•bookofjoe•1h ago•1 comments

Former JAGs say Hegseth, others may have committed war crimes

https://www.militarytimes.com/news/your-military/2025/12/01/former-jags-say-hegseth-others-may-ha...
6•petethomas•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•6mo 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•6mo 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•6mo 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•6mo 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.