frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

A Big Little Idea Called Legibility (2010)

https://www.ribbonfarm.com/2010/07/26/a-big-little-idea-called-legibility/
1•vismit2000•3m ago•0 comments

Show HN: A Clean Subnet Mask Cheat Sheet

https://subnetmaskcheatsheet.com
1•brianchanwh•3m ago•0 comments

Tell HN: Auto-download in Apple Podcasts is so unreliable it's basically useless

2•garyfirestorm•4m ago•0 comments

A simpler and more efficient fixed point iterative scheme

https://arxiv.org/abs/2601.05731
1•7777777phil•6m ago•0 comments

What Happens When Superhuman AIs Compete for Control? (From "AI 2027" Project)

https://blog.ai-futures.org/p/what-happens-when-superhuman-ais
1•TMWNN•7m ago•0 comments

Tired of code models giving you code iterations that crashes in production?

https://www.respcode.com
1•noormoha•8m ago•1 comments

Exact significance tests for 2 × 2 tables

https://janhove.github.io/posts/2024-09-10-contingency-p-value/
1•dbaupp•9m ago•0 comments

A personal password manager that works over SSH

https://alexlance.blog/encryption.html
1•alance•10m ago•1 comments

TweetGrok Twitter Viewer – Browse Public Tweets Without Logging In

https://tweetgrok.ai/twitter-viewer
1•Jennyyyy111•12m ago•1 comments

Three Inverse Laws of Robotics

https://susam.net/inverse-laws-of-robotics.html
1•todsacerdoti•13m ago•0 comments

Cloudflare CEO threatens the Winter Olympics after Italy slugs it with a fine

https://www.theregister.com/2026/01/12/cloudflare_vs_italy/
2•beardyw•15m ago•0 comments

Ideas are cheap, execution is cheaper

https://davekiss.com/blog/ideas-are-cheap-execution-is-cheaper/
1•grncdr•16m ago•0 comments

The great calculator debate: Educators disagree over their place in the classro

https://www.csmonitor.com/1986/0509/dcalc-f.html
1•todsacerdoti•21m ago•0 comments

SoleKey – A password manager with no PIN recovery, by design

https://play.google.com/store/apps/details?id=com.mdr.yapm&hl=en_US
1•ping_pundit•22m ago•1 comments

Show HN: I built a tool to visualize the Peter Thiel stock portfolio (13F data)

https://www.13radar.com/guru/peter-thiel
1•PanicSellGuru•29m ago•0 comments

Exasol Personal – Democratizing Big Data Analytics

https://www.exasol.com/blog/introducing-exasol-personal/
1•astigsen•32m ago•0 comments

Most US Gen Zers and millennials listen to about three hours of AI music a week

https://sherwood.news/markets/morgan-stanley-most-gen-zers-and-millennials-in-the-us-listen-to-ab...
1•croes•36m ago•1 comments

Demystifying Evals for AI Agents

https://www.anthropic.com/engineering/demystifying-evals-for-ai-agents
1•dvorka•43m ago•0 comments

I reverse engineered Ann Arbor's parking ticket system and built a live map

https://ammarateya.com/a2-parking/
4•ateya•45m ago•1 comments

The ESP32-C3 Super Mini Scam [video]

https://www.youtube.com/watch?v=ZMnSjpFgwdQ
2•josephcsible•47m ago•1 comments

HTGS – HTML Online Editor

https://htgspro.xyz/
1•MopAmine•48m ago•0 comments

Golden girl: Rose Byrne's Globes win maps the road to Oscar glory

https://www.smh.com.au/culture/movies/rose-byrne-golden-globes-winners-2026-oscar-win-best-actres...
1•keepamovin•48m ago•0 comments

AI Can Code (But It Doesn't Care About Quality)

https://blog.discourse.org/2026/01/ai-can-code-but-it-doesnt-care-about-quality/
1•mjrbrennan•51m ago•0 comments

A product that helps developers with marketing tools

https://amplift.ai/
1•gaygum102•52m ago•1 comments

UK Prime Minister Starmer seeks support for international X ban

https://www.euractiv.com/news/uk-prime-minister-starmer-seeks-support-for-international-x-ban/
4•saubeidl•54m ago•5 comments

WhatsApp is untrustable

https://toki.la/posts/whatsapp
4•purglet•56m ago•0 comments

Common misunderstandings about large software companies

https://philipotoole.com/common-misunderstandings-about-large-software-companies/
1•otoolep•56m ago•0 comments

The Emacs Widget Library: A Critique and Case Study

https://www.d12frosted.io/posts/2025-11-26-emacs-widget-library
1•whacked_new•57m ago•0 comments

The liquid air alternative to fossil fuels

https://www.bbc.com/future/article/20251009-the-liquid-air-alternative-to-fossil-fuels
1•otoolep•58m ago•0 comments

DroPE: Extending the Context of LLMs by Dropping Their Positional Embeddings

https://pub.sakana.ai/DroPE/
3•hardmaru•58m 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.