frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenRouter requests to MiniMax models may have been read

https://www.reddit.com/r/LocalLLaMA/comments/1y1we95/openrouter_requests_to_minimax_models_may_have/
1•ksec•1m ago•0 comments

AWS local emulator created by AI agents

https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/
1•wenbert•8m ago•0 comments

The quantum computing race is becoming a deployment race

https://www.techradar.com/pro/the-quantum-computing-race-is-becoming-a-deployment-race
1•jonbaer•15m ago•0 comments

'I was shaking, crying, having trouble breathing': the uncharted trauma

https://www.theguardian.com/technology/ng-interactive/2026/nov/21/shaking-crying-trouble-breathin...
1•user20180120•18m ago•1 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
2•tamnd•18m ago•0 comments

WikiLLM: Browse language model weights like an encyclopedia

https://github.com/eagleclaw0075/wikillm/
1•havemurci•21m ago•0 comments

Show HN: Npx.tools, a keyboard-friendly index of developer tools

https://npx.tools/
1•hasnainkhagan•25m ago•0 comments

AI as a Lifestyle Choice

https://grahamdumpleton.me/posts/2026/11/ai-as-a-lifestyle-choice/
1•Karrot_Kream•36m ago•0 comments

California Nvidia Probe Covers Potential Criminal Law Violations

https://www.bloomberg.com/news/articles/2026-11-21/california-nvidia-probe-covers-potential-crimi...
2•petethomas•39m ago•0 comments

Ask HN: What made you pivot your interest to the field of AI?

4•learner_yearner•45m ago•2 comments

The Explorer Pattern for product invention and development

https://lethain.com/explorer-pattern/
1•gpi•45m ago•0 comments

Replaced PTX with MLIR, cutting asm regions from 499 to 81 across 20 kernels

https://vxlang.org/blog/handing-the-ptx-back-to-the-compiler.html
3•reshabh•46m ago•0 comments

San Francisco Braces for Record Tides as Mayor Urges Residents to Stay Put

https://kfn.one/news/san-francisco-braces-for-record-tides-as-mayor-urges-1d795047
1•reena•47m ago•0 comments

Back Pain (2021)

https://www.thomas-huehn.com/back-pain/
1•Curiositry•47m ago•0 comments

AI Supply Chain Security: What Canary Tokens Found

https://www.dragos.com/blog/ai-supply-chain-security-canary-tokens
2•kristianp•53m ago•0 comments

Replaying an agent run and what it takes

https://github.com/chizy7/tether/blob/master/docs/REPLAY.md
1•chizy7•54m ago•0 comments

Trump threatens penalties for US tech firms that build datacenters abroad

https://www.theguardian.com/us-news/2026/nov/20/trump-datacenters-white-house
4•Pxtl•55m ago•1 comments

AiDotNet – Comprehensive AI/ML Framework for .NET

https://github.com/ooples/AiDotNet
2•olvy0•58m ago•0 comments

Why founders say launch directories send little traffic, and how they judge them

https://mambatxhub.com
1•aishabethuel127•59m ago•0 comments

Strangler pattern, a powerful simple concept to do refactoring (2019)

https://martinfowler.com/bliki/StranglerFigApplication.html
1•zenincognito•1h ago•0 comments

ING's $500M Data Center Loan Auction Stalls on Weak Demand

https://www.bloomberg.com/news/articles/2026-11-20/ing-s-500-million-data-center-loan-auction-sta...
1•cobychapple•1h ago•0 comments

Job ghosting: What applicants can do if employers do not respond

https://www.bbc.com/news/articles/cm2d94le23xyo
3•rustoo•1h ago•0 comments

Userscript managers in 2026: what Manifest V3 changed

https://www.softwr.com/news/best-userscript-managers
2•peter_d_sherman•1h ago•1 comments

"Dumbass" RFK Jr. Rescued Measles from Obscurity. What Horror Is Next?

https://newrepublic.com/post/218245/rfk-jr-measles-trump-outbreak
10•petethomas•1h ago•2 comments

What It Looks Like to Parent Without Gender

https://www.thenation.com/article/society/what-it-looks-like-to-parent-without-gender/
3•petethomas•1h ago•0 comments

One Vulnearbility Hacks Google, WordPress, Roundcube, Debian 13, Zoom, Box, etc.

https://pwn.ai/upload2shell/research.html
3•lovetoseeitgeth•1h ago•1 comments

A Collision for 38-Step SHA-256

https://eprint.iacr.org/2026/2913
1•gslin•1h ago•0 comments

NixOS bring-up on an Alibaba RISC-V board

https://feyor.sh/blog/nixos-bringup-on-an-alibaba-riscv-board/
2•todsacerdoti•1h ago•1 comments

Trump at the "Summit": One of His Dumbest Moments in the Last 10 Years

https://newrepublic.com/post/218235/trump-summit-xi-putin-nuclear
5•petethomas•1h ago•0 comments

Show HN: Vouch – See what AI assistants say about your brand mid-conversation

https://vouchgeo.com
1•samratkar•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•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.