frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

AI-Declaration.md

https://github.com/DimwitLabs/AI-DECLARATION.md
1•rapiz•1m ago•0 comments

AI Prompt Examples and Techniques for Better AI Outputs

https://promptessor.com/blog/10-ai-prompt-examples-and-techniques
1•rizkimurtadha•1m ago•0 comments

Waterloo Intern = Head of Infra

https://twitter.com/waterloo_intern/status/2057977885840036104
1•tuhins•4m ago•0 comments

Nvidia Removes Gaming Revenue Category from Financial Reports

https://www.guru3d.com/story/nvidia-removes-gaming-revenue-category-from-financial-reports/
1•theanonymousone•4m ago•0 comments

Show HN: Pilates – pure TypeScript flex layout for terminal UIs

https://github.com/pilatesjs/pilates
1•wangzhijie•6m ago•0 comments

Nuclear Power in China

https://world-nuclear.org/information-library/country-profiles/countries-a-f/china-nuclear-power
1•leonidasrup•7m ago•0 comments

Destino: Doom in Your Terminal with Node.js

https://blog.platformatic.dev/destino-doom-terminal-nodejs-ffi
1•piraccini•11m ago•0 comments

Show HN: Source screen for congressional stock disclosure claims

https://tinyopsstudio.com/congress-disclosure-now-csco-source-screen
1•tinyopsstudio•13m ago•0 comments

Telegram's MTProto: Assessing Deanonymization Potential for a Network Attacker [pdf]

https://symbolic.software/pdf/gnmx-01.pdf
1•sysoleg•15m ago•0 comments

Arsenal's title win should be studied by politicians everywhere

https://www.theguardian.com/commentisfree/2026/may/22/keir-starmer-arsenal-politics-premier-league
1•teleforce•25m ago•0 comments

Strengthening Singapore's AI Future

https://deepmind.google/blog/strengthening-singapores-ai-future-a-new-national-partnership/
2•pretext•26m ago•0 comments

Microsoft Agrees to $250M Settlement with Activision Blizzard Shareholders

https://www.law.com/delbizcourt/2026/05/22/microsoft-agrees-to-250m-settlement-with-activision-bl...
2•1vuio0pswjnm7•26m ago•0 comments

White House ordering agencies to place its new app on all employees' govt phones

https://www.govexec.com/management/2026/05/white-house-ordering-agencies-place-its-new-app-all-em...
1•mikhael•26m ago•0 comments

US tells foreigners seeking green cards: Return to your countries to apply

https://www.reuters.com/legal/government/uscis-tells-foreigners-seeking-green-cards-return-your-c...
1•tartoran•27m ago•0 comments

Publishing's Latest Piracy Problem: Audiobooks on YouTube

https://www.nytimes.com/2026/05/21/books/audiobook-piracy-youtube.html
1•thm•30m ago•0 comments

Judge considers ordering Meta to revamp its apps

https://www.politico.com/news/2026/05/22/meta-judge-trial-public-nuisance-facebook-00934485
1•1vuio0pswjnm7•31m ago•0 comments

Crypto industry braces for quantum computing threat

https://www.ft.com/content/99c1c1e7-1a1c-479c-9fc8-e21aea5c3f0e
5•thm•33m ago•1 comments

Waymo suspends all freeway rides over safety

https://www.latimes.com/business/story/2026-05-22/waymo-suspends-all-freeway-rides-over-safety
2•1vuio0pswjnm7•33m ago•0 comments

Starbucks scraps AI inventory tool after nine months

https://qz.com/starbucks-scraps-ai-inventory-tool-nomadgo-052226
2•thunderbong•33m ago•0 comments

In India, You Can Get Milk Delivered Faster Than It Takes to Make Coffee

https://www.wsj.com/business/logistics/in-india-you-can-get-milk-delivered-faster-than-it-takes-t...
2•JumpCrisscross•34m ago•0 comments

Google appeals search monopoly ruling, says it won business 'fair and square'

https://www.theverge.com/policy/936175/google-search-monopoly-ruling-appeal
2•thm•35m ago•0 comments

Cannes Film Cost $500k to Make. $400k Was AI Compute Costs

https://www.wsj.com/cio-journal/this-cannes-film-cost-500-000-to-make-400-000-was-ai-compute-cost...
5•JumpCrisscross•36m ago•0 comments

How to Be a Real Elite Programmer

https://skorks.com/2010/05/how-to-be-a-real-elite-programmer-and-make-sure-everybody-knows-it/
2•mahirsaid•39m ago•0 comments

The Fonts of the U.S. Federal Courts

https://daringfireball.net/2026/05/the_fonts_of_the_us_federal_courts
1•Tomte•42m ago•0 comments

Microsoft's new multi-model agentic security system tops leading benchmark

https://www.microsoft.com/en-us/security/blog/2026/05/12/defense-at-ai-speed-microsofts-new-multi...
3•uniclaude•48m ago•0 comments

Lisa's Copy (and Cut, and Paste)

https://unsung.aresluna.org/lisas-copy-and-cut-and-paste/
1•zdw•52m ago•0 comments

Is U.S. AI Adoption Plateauing? A Comprehensive Analysis

https://medium.com/@markchen69/is-u-s-ai-adoption-plateauing-a-comprehensive-analysis-cf5c1beef8cf
2•mgh2•56m ago•0 comments

Introducing BDD (2006)

https://dannorth.net/blog/introducing-bdd/
1•locknitpicker•57m ago•0 comments

Computing the billionth prime in 1s with LLVM IR

https://github.com/SheafificationOfG/QueenJewels
1•Murfalo•58m ago•1 comments

Is AI Becoming Too Smart for Its Own Good? [audio]

https://rss.com/podcasts/nuclecast-podcast/2811653/
1•apolloartemis•59m ago•1 comments
Open in hackernews

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

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