frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Gimp devs take control of Snap package from Snapcrafters

https://www.neowin.net/news/gimp-devs-take-official-control-of-snap-package-from-snapcrafters/
1•bundie•5m ago•0 comments

GoFundMe CEO: economy is so bad his customers crowdfund to pay for groceries

https://finance.yahoo.com/news/gofundme-ceo-says-economy-bad-182843671.html
2•sudonanohome•14m ago•0 comments

Italian blasphemy and German ingenuity: how swear words differ around the world

https://www.theguardian.com/science/2025/oct/19/italian-blasphemy-and-german-ingenuity-how-swear-...
1•sandebert•15m ago•0 comments

Show HN: Translating dog behaviors into human language using AI

https://dogtranslator.org/
1•reverseCh•28m ago•0 comments

Orca-trackers harness telecoms cable network

https://divernet.com/scuba-news/marine-biology/orca-trackers-harness-telecoms-cable-network/
1•pooyamehri•43m ago•0 comments

Programming language agnosticism is the only way to move forward in life

3•amano-kenji•49m ago•0 comments

Organizing your Nix configuration without flakes

https://somas.is/note-organizing-nix-configuration-without-flakes.html
1•amcclure•50m ago•0 comments

Volvelle, an early example of a paper analog computer

https://en.wikipedia.org/wiki/Volvelle
1•valzevul•58m ago•0 comments

The Launchpad macOS 26 deserves

https://www.launchie.app
1•nickfthedev•1h ago•0 comments

Dumper: CLI utility for creating database backups – PostgreSQL, MySQL and others

https://github.com/elkirrs/dumper
2•thunderbong•1h ago•0 comments

Scientists Discover How Leukemia Cells Evade Treatment

https://www.rutgers.edu/news/scientists-discover-how-leukemia-cells-evade-treatment
1•geox•1h ago•0 comments

The Inevitable Shift from Prompts to Answers

https://www.aivojournal.org/the-inevitable-shift-from-prompts-to-answers/
2•businessmate•1h ago•1 comments

BoE chief: Brexit impact on UK economy negative for foreseeable future

https://news.sky.com/story/brexit-impact-on-uk-economy-negative-for-foreseeable-future-bank-of-en...
4•teleforce•1h ago•0 comments

I wish SSDs gave you CPU performance style metrics about their activity

https://utcc.utoronto.ca/~cks/space/blog/tech/SSDWritePerfMetricsWish
1•zdw•1h ago•0 comments

Lightning Computational Graph Theory

https://www.youtube.com/watch?v=A-z2ZIMWbuY
3•_untra_•1h ago•0 comments

But AI companies grow so fast

https://99d.substack.com/p/but-ai-companies-grow-so-fast
2•airstrike•1h ago•0 comments

Researchers find adding simple sentence to prompts makes AI models more creative

https://venturebeat.com/ai/researchers-find-adding-this-one-simple-sentence-to-prompts-makes-ai-m...
3•jdnier•1h ago•0 comments

Mortality in the news vs. what we usually die from

https://flowingdata.com/2025/10/08/mortality-in-the-news-vs-what-we-usually-die-from/
2•paulpauper•1h ago•0 comments

What I Learned from Lifting

https://www.atvbt.com/what-i-learned-from-lifting/
2•paulpauper•1h ago•0 comments

Another axiom that Euclid missed

https://web.archive.org/web/20250821165148/https://mathenchant.wordpress.com/2025/01/17/the-real-...
2•gsf_emergency_4•1h ago•0 comments

Show HN: NoCloud Bulk Image Converter (Cross-Platform, Privacy-First)

https://github.com/goto-eof/noc-convert
1•cbrx31•1h ago•1 comments

Dive-computer evidence ignored after 12yr-old's death

https://divernet.com/scuba-news/health-safety/death/dive-computer-evidence-ignored-after-12yr-old...
3•pooyamehri•1h ago•2 comments

Show HN: Drag to AirDrop

https://sindresorhus.com/menu-drop
3•mofle•1h ago•2 comments

Kintsugi Love

https://asim.bearblog.dev/kintsugi-love/
4•asim-shrestha•2h ago•1 comments

The traffickers are winning the war on drugs

https://www.economist.com/briefing/2025/10/16/the-traffickers-are-winning-the-war-on-drugs
26•coloneltcb•2h ago•19 comments

'Girl Take Your Crazy Pills ': Antidepressants Recast as Hot Lifestyle Accessory

https://www.wsj.com/health/wellness/anti-depressants-lifestyle-accessory-3b66027d
6•clanky•2h ago•2 comments

Zeno – open-source AI assistant that turns ideas into tasks

https://zenoapp.site/
2•CrazyCompiler01•2h ago•0 comments

Progress on defeating lifetime-end pointer zapping

https://lwn.net/Articles/1038757/
1•pykello•2h ago•0 comments

Wealth AI – Your Personal AI CFO That Understands Every Rupee You Spend

https://www.sideprojectors.com/project/67099/wealthai
2•WoWSaaS•2h ago•0 comments

Nutrition Beliefs Are Just-So Stories

https://www.cremieux.xyz/p/nutrition-beliefs-are-just-so-stories
5•smnthermes•2h ago•1 comments
Open in hackernews

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

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