frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Information Asymmetry

https://en.wikipedia.org/wiki/Information_asymmetry
1•downboots•10m ago•1 comments

Malicious Checkmarx Artifacts Found in Official KICS Docker Repo and Code Ext

https://socket.dev/blog/checkmarx-supply-chain-compromise
1•orkj•11m ago•0 comments

Show HN: CreepJS Browser Fingerprinting

https://abrahamjuliot.github.io/creepjs/
2•gastonmorixe•12m ago•0 comments

Sruthi Chandran Elected Debian Project Leader

https://bits.debian.org/2026/04/dpl-elections-2026.html
1•tapanjk•16m ago•0 comments

Every local SEO playbook is built on proximity, AI overviews ignore it completly

https://webmatrices.com/post/every-local-seo-playbook-is-built-on-proximity-ai-overviews-ignore-i...
1•bishwasbh•17m ago•0 comments

Ars Technica: Our newsroom AI policy

https://arstechnica.com/staff/2026/04/our-newsroom-ai-policy/
2•zdw•22m ago•1 comments

Computing in the Era of Doom: What Were PCs Like in 1993?

https://www.ahalbert.com/reviews/technology/2026/04/20/black-book-doom.html
1•pjmlp•25m ago•0 comments

High Street mini-marts selling cocaine, cannabis and prescription drugs

https://www.bbc.co.uk/news/articles/c62l429w2pko
1•vinni2•27m ago•0 comments

A disabled kea parrot is the alpha male of his circus

https://www.cell.com/current-biology/fulltext/S0960-9822(26)00259-9
1•zdw•28m ago•0 comments

Ford pivoting to catch up with his real competitor: China's BYD

https://finance.yahoo.com/sectors/technology/articles/ford-ceo-says-tesla-doesn-180115430.html
1•KnuthIsGod•30m ago•0 comments

Bloom filters: the niche trick behind a 16× faster API

https://incident.io/blog/bloom-filters
2•crcastle•40m ago•1 comments

Cursor and SpaceX: In search of a complete loop

https://kwokchain.com/2026/04/23/cursor-and-spacex-in-search-of-a-complete-loop/
1•borisjabes•41m ago•0 comments

Show HN: Viscacha - A crashsafe, zero infra job system for funcs/AI pipelines

https://github.com/skylarm-b/viscacha
1•SkyguyMB•43m ago•0 comments

House lawmakers get a chilling demo of 'jailbroken' AI

https://www.politico.com/news/2026/04/22/ai-chatbots-jailbreak-safety-00887869
1•0in•50m ago•1 comments

Anthropic has surged to a trillion-dollar valuation on secondary markets

https://www.businessinsider.com/anthropic-trillion-dollar-valuation-on-secondary-markets-2026
1•Growtika•50m ago•0 comments

I am building a cloud

https://crawshaw.io/blog/building-a-cloud
37•bumbledraven•52m ago•4 comments

Half of AI health answers are wrong even though they sound convincing

https://theconversation.com/half-of-ai-health-answers-are-wrong-even-though-they-sound-convincing...
1•KnuthIsGod•52m ago•0 comments

Iran's IRGC warns it may cut undersea internet cables in Persian Gulf

https://www.msn.com/en-in/money/news/iran-s-irgc-warns-it-may-cut-undersea-internet-cables-in-per...
2•KnuthIsGod•53m ago•3 comments

Open source is not the problem, but its misuse by corporations

https://www.heise.de/en/blog/Open-source-is-not-the-problem-but-its-misuse-by-corporations-112667...
1•goloroden•53m ago•0 comments

ChatGPT for Clinicians

https://twitter.com/thekaransinghal/status/2047091103170785324
1•stenlix•55m ago•0 comments

MacBook Neo and How the iPad Should Be

https://craigmod.com/essays/ipad_neo/
1•jen729w•55m ago•0 comments

'Intelligence may be scalable, but accountability is not'

https://www.msn.com/en-us/news/technology/intelligence-may-be-scalable-but-accountability-is-not-...
1•galaxyLogic•55m ago•0 comments

DragonRuby's Seventh Year – Where We Started and Where We're Going

https://dragonruby.itch.io/dragonruby-gtk/devlog/1497015/dragonrubys-seventh-year-where-we-starte...
3•doppp•1h ago•0 comments

Pokemon Red and the Evolution of FSM

https://www.makonea.com/en-US/blog/Pokemon-Red-and-the-Evolution-of-FSM
1•jdw64•1h ago•0 comments

Hackers tricked Sri Lanka's Treasury into sending $2.5M to the wrong account

https://www.ft.lk/top-story/Treasury-rocked-by-2-5-m-fraud/26-791019
1•oshanz•1h ago•0 comments

MartinLoop – The control plane for autonomous AI agents

https://github.com/Keesan12/martin-loop
1•martinloop•1h ago•0 comments

In the age of AI, why do Australian company boards have few technology experts?

https://theconversation.com/in-the-age-of-ai-why-do-australian-company-boards-have-so-few-technol...
1•indynz•1h ago•1 comments

Low Contrast UI Pandemic

1•mr-pink•1h ago•1 comments

A Boy That Cried Mythos: Verification Is Collapsing Trust in Anthropic

https://www.flyingpenguin.com/the-boy-that-cried-mythos-verification-is-collapsing-trust-in-anthr...
36•taejavu•1h ago•8 comments

Choose Boring Technology

https://mcfunley.com/choose-boring-technology
1•doppp•1h ago•1 comments
Open in hackernews

Show HN: Brainfuck to RISC-V JIT compiler written in Zig

https://github.com/evelance/brainiac
5•0x000xca0xfe•11mo 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•11mo 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•11mo 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•11mo 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.