frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Vibe Commander

https://github.com/AvitalTamir/vibecommander
2•fatliverfreddy•11m ago•0 comments

Bcachefs 1.33.0 – Reconcile

https://lore.kernel.org/linux-bcachefs/slvis5ybvo7ch3vxh5yb6turapyq7hai2tddwjriicfxqivnpn@xdpb25w...
1•RGBCube•12m ago•0 comments

Updating My Bash Prompt

https://martianlantern.github.io/2025/11/updating-my-bash-prompt/
2•martianlantern•22m ago•0 comments

Robotgo v1.0.0 and Pro, easy build automation, auto test, computer use

https://github.com/go-vgo/robotgo/releases/tag/v1.0.0
2•veni0•23m ago•0 comments

South Korea developing app that shows real-time location of stalkers

https://www.bbc.com/news/articles/cp84y7jx2pzo
2•1659447091•23m ago•0 comments

The Long, Knotty, World-Spanning Story of String

https://hakaimagazine.com/features/the-long-knotty-world-spanning-story-of-string/
2•bookofjoe•25m ago•0 comments

Blogging in 2025: Screaming into the Void

https://askmike.org/articles/blogging-in-2025-screaming-into-the-void/
2•askmike•27m ago•0 comments

Apple iOS 27 to Be No-Frills 'Snow Leopard' Update

https://www.bloomberg.com/news/newsletters/2025-11-23/apple-ios-27-snow-leopard-like-quality-focu...
1•dlx•28m ago•1 comments

Billionaire UBS Clients Plot Private Equity Funds' Retreat

https://www.bloomberg.com/news/articles/2025-12-04/billionaire-ubs-clients-plot-retreat-from-priv...
1•petethomas•31m ago•0 comments

EU plans five AI gigafactories with 100k high-performance AI chips

https://the-decoder.com/eu-plans-five-ai-gigafactories-with-100000-high-performance-ai-chips/
3•Vaslo•31m ago•1 comments

Stacktower: An Accidental Deep Dive

https://stacktower.io/
2•signa11•32m ago•0 comments

CDC vaccine panel realizes again it has no idea what it's doing, delays big vote

https://arstechnica.com/health/2025/12/cdc-vaccine-panel-realizes-again-it-has-no-idea-what-its-d...
3•voxadam•36m ago•0 comments

Ukraine's 'Crazy' New Drone Tech [video]

https://www.youtube.com/watch?v=bsy5xzdKahU
1•thomassmith65•39m ago•0 comments

Chinese-linked hackers use back door for potential 'sabotage,' US and Canada say

https://www.reuters.com/world/china/chinese-linked-hackers-use-back-door-potential-sabotage-us-ca...
6•737min•42m ago•0 comments

Gemini 3 Deep Think is now available in the Gemini app

https://blog.google/products/gemini/gemini-3-deep-think/
1•jamesyun•47m ago•0 comments

Life_logger – Turn your daily experiences into retro thermal receipt-style logs

https://life-logger.netlify.app/
2•Eyoz•49m ago•1 comments

Ask HN: How do LLMs perform in the low-level space?

1•kode-targz•51m ago•0 comments

Our Commitment to Your Ongoing Success with Discourse

https://blog.discourse.org/2025/12/our-commitment-to-your-ongoing-success-with-discourse/
1•kevmarsden•51m ago•1 comments

PublicQ – Free Open Source Assessment and Exam Platform

https://publicq.app/
2•mtokarev•53m ago•0 comments

80s version of Tinder was 'video dating' was incredibly awkward (2015)

https://www.businessinsider.com/found-footage-awkward-80s-video-dating-2015-12
1•raw_anon_1111•57m ago•0 comments

Untapped Potential in the Java Build Tool Experience

https://javapro.io/2025/10/23/untapped-potential-in-the-java-build-tool-experience/
1•lihaoyi•1h ago•0 comments

Show HN: WishKeeper – Gift coordination that keeps the surprise alive

https://wishkeeper.io
1•colinmilhaupt•1h ago•0 comments

You can now text and drive in Tesla's (during FSD)

https://twitter.com/elonmusk/status/1996631421449072754
2•ryanvogel•1h ago•1 comments

Lyrics viewer for Linux that integrates with MPRIS

https://github.com/BEST8OY/LyricsMPRIS-Rust
2•amadeuspagel•1h ago•0 comments

Show HN: Flooder – Making Persistent Homology Practical for Industrial Use Cases

https://plus-rkwitt.github.io/flooder/
2•elektm•1h ago•2 comments

You may loose your company email, but never lose your emails and contacts again

https://app.trevally.io/login.html
4•danvc•1h ago•11 comments

Do We Understand SQL?

https://www.youtube.com/watch?v=qiVUf9X6ItM
1•jamii•1h ago•0 comments

The Disappearance of an Anti-AI Activist

https://www.theatlantic.com/technology/2025/12/sam-kirchner-missing-stop-ai/685144/
12•fortran77•1h ago•2 comments

The Future of AI Code Review: From Bug Detection to Compliance Guardianship

https://codeprot.com/articles/ai-code-review-future.html
1•allenz_cheung•1h ago•1 comments

Ultrasonic device dramatically speeds harvesting of water from the air

https://news.mit.edu/2025/ultrasonic-device-dramatically-speeds-harvesting-water-air-1118
13•bookofjoe•1h ago•5 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.