frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Math Grid – Japan's 100-square math drill (hyakumasu keisan)

https://apps.apple.com/ca/app/math-grid-100-squares/id6779562830
1•emile_labs•2m ago•0 comments

Cutting China reliance would cost the West $23T, research suggests

https://www.ft.com/content/c6c1f5a5-3332-471b-87d5-253e03f8b90a
1•giuliomagnifico•4m ago•0 comments

Gofi – go tooling for Ubiquiti Unifi gear

https://github.com/emergingrobotics/gofi
1•gherlein•5m ago•0 comments

Ampere, open-source battery charge control for Apple Silicon Macs

https://amperebattery.app/
1•elgs•5m ago•0 comments

Recognition of unfamiliar predators in horses through only visual predator cues

https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0349298
1•bookofjoe•6m ago•0 comments

Humans evolved to be twice as big as our ancestors

https://www.newscientist.com/article/2533221-how-humans-evolved-to-be-twice-as-big-as-our-ancestors/
1•ike_usawa•7m ago•0 comments

Neglected software update caused widespread Telstra network outage

https://www.theguardian.com/business/2026/jul/17/telstra-missing-software-update-undocumented-des...
1•prawn•7m ago•0 comments

Get notified about open slots at campgrounds / huts / cabins all over the world

https://getcabinfever.com/en/last-minute
1•felixdoerp•7m ago•0 comments

50 vs. 60 Hz and Alzheimer's Disease, an AI Exploration

https://github.com/mankins/50Hz-vs-60Hz-Alzheimers
1•mankins•9m ago•0 comments

Should AI usage be explicitly disclosed in movies and TV shows?

https://www.unite.ai/should-ai-usage-be-explicitly-disclosed-in-movies-and-tv-shows/
1•50kIters•10m ago•0 comments

Value, quality or growth: three investing philosophies based on 12 years of data

https://aito.ai/blog/value-quality-or-growth-who-was-right/
1•arauhala•10m ago•0 comments

Zero Weights Deterministic Graph Language Model (MSE-GLM)

https://tonlexianert.com/pages/blog.php
1•clifffodokidza•14m ago•0 comments

Ask HN: Best courses/resources to learn SEO?

1•danilovilhena•15m ago•0 comments

Why AI Infrastructure Is Becoming More Important Than AI Models

https://geekyants.com/blog/self-healing-ai-agents-the-future-of-enterprise-automation-needs-gover...
2•maria46•16m ago•0 comments

Blatant AI slop just won a 25k USD DeepMind Kaggle Grand Prize

https://www.kaggle.com/competitions/kaggle-measuring-agi/discussion/724918#3498423
45•twerkmeister•19m ago•4 comments

Show HN: Tiny and CSP-safe expression language for JavaScript

https://github.com/robinvdvleuten/xprsn
1•robinvdvleuten•22m ago•0 comments

Windows XP Simulation by Kimi K3

https://windows-xp.kimi.site/
2•uneven9434•25m ago•0 comments

Ask HN: Whats the worst site that you have encountered for accessibility?

2•a11ymaster•26m ago•1 comments

Get your FREE custom Email

https://bottled.email
1•Spark88•34m ago•2 comments

EU to force Google to share search data and open up AI on Android

https://arstechnica.com/gadgets/2026/07/its-official-eu-will-force-google-to-share-search-data-an...
3•goplayoutside•45m ago•1 comments

Show HN: Vulnsy – A platform for vulnerability management and reporting

https://www.vulnsy.com
1•MrTurvey•47m ago•0 comments

Now, even Russia's most elite hackers are using Clickfix to infect devices

https://arstechnica.com/security/2026/07/now-even-russias-most-elite-hackers-are-using-clickfix-t...
2•joozio•47m ago•0 comments

ScreenWall – Turn old phones into synced widgets for your space

https://screenwall.app/
2•buibuibui•49m ago•0 comments

Soofi – Sovereign Open Source Foundation Models

https://www.soofi.info/
1•sebastian_z•49m ago•0 comments

Rokit to launch what it calls first human kidney regeneration surgery in July

https://www.koreabiomed.com/news/articleView.html?idxno=32016
1•deno•51m ago•0 comments

Show HN: Sandboxd – Self-Hosted Lovable (agents, sandboxes, preview url)

https://github.com/tastyeffectco/sandboxd
1•tastyeffectco•51m ago•1 comments

What Early Hackers Got Right About Today's AI [video]

https://www.youtube.com/watch?v=XHeMsXDyw2A
1•pierrephpguru•58m ago•2 comments

Huawei could become a DRAM fabber

https://www.blocksandfiles.com/ai-ml/2026/07/16/huawei-could-become-a-dram-fabber/5273853
2•rbanffy•59m ago•0 comments

Show HN: Customizable SAP MCP Server

https://superglue.ai/mcp/sap/
1•sfaist•59m ago•0 comments

Comptime Is Funtime: Per-Span State Without a Hash Map

https://david-bach.com/pages/posts/2026-07-15-comptime-is-funtime/index.html
1•eoxxs•1h ago•0 comments
Open in hackernews

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

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