frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

European parliament calls for social media ban on under-16s

https://www.theguardian.com/technology/2025/nov/26/social-media-ban-under-16s-european-parliament...
2•2OEH8eoCRo0•3m ago•1 comments

MCPs for Developers Who Think They Don't Need MCPs

https://block.github.io/goose/blog/2025/11/26/mcp-for-devs/
1•gmays•5m ago•0 comments

Germany's pension reform becomes a generational conflict

https://www.lemonde.fr/en/international/article/2025/11/27/germany-s-pension-reform-becomes-a-gen...
1•throw0101c•7m ago•1 comments

Devconnect 2025 Recap: What You Might Have Missed in Buenos Aires

https://thomasbenoitbenoitonchain.substack.com/p/devconnect-2025-recap-what-you-might
2•benoitonchainyc•7m ago•1 comments

China's Alibaba brings removable batteries to the smart glasses race

https://www.theverge.com/news/831354/alibaba-quark-smart-glasses
2•mgh2•9m ago•0 comments

Rare microbial relict sheds light on an ancient eukaryotic supergroup

https://www.nature.com/articles/s41586-025-09750-0
1•nhatcher•10m ago•1 comments

Alibaba starts selling Quark AI glasses in China, enters global wearables race

https://www.reuters.com/world/china/alibaba-starts-selling-quark-ai-glasses-china-enters-global-w...
1•mgh2•10m ago•0 comments

Scientists may have detected dark matter

https://phys.org/news/2025-11-years-scientists-dark.html
1•erikrozendaal•12m ago•0 comments

Evaluating Uniform Memory Access Mode on AMD's Turin Ft. Verda

https://chipsandcheese.com/p/evaluating-uniform-memory-access
1•rbanffy•12m ago•0 comments

BBC tells staff they cannot quote Trump line removed from Reith Lecture

https://www.theguardian.com/media/2025/nov/27/bbc-donald-trump-corruption-line-removed-from-rutge...
7•INGELRII•13m ago•1 comments

DeepMind "The Thinking Game" now free on YouTube [video]

https://www.youtube.com/watch?v=d95J8yzvjbQ
2•HarHarVeryFunny•14m ago•1 comments

Comparing the Genesis Mission to the Manhattan Project

https://tickerfeed.net/articles/whitehouse-genesis-mission-bailout-openai-nvidia
2•sethops1•14m ago•0 comments

Plex's crackdown on free remote streaming access starts this week

https://arstechnica.com/gadgets/2025/11/plexs-crackdown-on-free-remote-streaming-access-starts-th...
2•throwawayffffas•15m ago•0 comments

Stirling PDF v2.0 Released

https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v2.0.0
2•chromehearts•15m ago•0 comments

HP to Cut Up to 10% of Workforce as Part of AI Push

https://www.wsj.com/tech/hp-to-cut-up-to-10-of-workforce-as-part-of-ai-push-a2c198da
2•bookofjoe•16m ago•1 comments

How to Get Hired in 2025

https://tonsky.me/blog/hiring-ai/
2•whereistejas•17m ago•0 comments

Bringing Emacs Support to OCaml's LSP Server with OCaml-Eglot

https://tarides.com/blog/2025-11-27-bringing-emacs-support-to-ocaml-s-lsp-server-with-ocaml-eglot/
1•nukifw•17m ago•0 comments

Nvidia rumored to stop bundling memory with GPUs, squeezing smaller partners

https://videocardz.com/newz/nvidia-rumored-to-stop-bundling-memory-with-gpus-squeezing-smaller-bo...
3•davikr•19m ago•0 comments

Time it's not fatigue, but disconnection

https://morrick.me/archives/10176
1•milen•24m ago•0 comments

Game Theory in Cosmology

https://arxiv.org/abs/2511.20739
2•johnsutor•25m ago•0 comments

Place Capability Graphs: A General-Purpose Model of Rust's Ownership & Borrowing [video]

https://www.youtube.com/watch?v=JcQX8raHWQE
1•matt_d•26m ago•0 comments

Show HN: I made a white noise generator for my newborn

https://whitenoise.now/
2•vicke4•26m ago•0 comments

Tell HN: OpenAI Security Incident with PII

2•vintagedave•26m ago•1 comments

China tech giants move AI training offshore to tap Nvidia chips

https://www.semafor.com/article/11/27/2025/china-tech-giants-move-ai-model-training-offshore-to-t...
1•giuliomagnifico•28m ago•0 comments

Renewing GPG Subkeys in 2025

https://entropicthoughts.com/renewing-gpg-subkeys-in-2025
2•ibobev•29m ago•0 comments

Show HN: Alice Architecture: An Attempt at Autonomous AGI Based on ±0 Theory

https://github.com/xian367422611213344-source/Alice-Architecture-based-on-pm0-core
1•Norl-Seria•29m ago•1 comments

TPUs vs. GPUs and why Google is positioned to win AI race in the long term

https://www.uncoveralpha.com/p/the-chip-made-for-the-ai-inference
3•vegasbrianc•29m ago•0 comments

Campbell's fires executive who criticised its food in recording

https://www.ft.com/content/47444ad2-03ef-4064-8d06-cd752d1e383c
2•bookofjoe•30m ago•2 comments

How to use ChatGPT without brainrot

https://davidepstein.substack.com/p/how-to-use-chatgpt-without-brain
3•call-me-al•30m ago•0 comments

DeepSeekMath-V2: Towards Self-Verifiable Mathematical Reasoning

https://github.com/deepseek-ai/DeepSeek-Math-V2
2•chenzhekl•31m 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.